Ryan Schultz
8afacf268a
- Hover provider showing entity information and type - Go-to-definition (F12) for entity references - Basic IFC file validation (ISO-10303-21 header check) - Entity parsing with regex-based detection - Proper CommonJS module system (avoiding ES module issues) This replaces the broken baseline from ifc-developer-tools which had: - Non-functional ES module configuration - Circular dependency issues - Parser crashes - Non-working PositionVisitor Built on Microsoft's LSP example template for a clean, maintainable foundation. Next: Add hierarchical entity dependency tree in hover tooltip."
17 lines
No EOL
788 B
TypeScript
17 lines
No EOL
788 B
TypeScript
import { MinimatchOptions } from './index.js';
|
|
/**
|
|
* Un-escape a string that has been escaped with {@link escape}.
|
|
*
|
|
* If the {@link windowsPathsNoEscape} option is used, then square-brace
|
|
* escapes are removed, but not backslash escapes. For example, it will turn
|
|
* the string `'[*]'` into `*`, but it will not turn `'\\*'` into `'*'`,
|
|
* becuase `\` is a path separator in `windowsPathsNoEscape` mode.
|
|
*
|
|
* When `windowsPathsNoEscape` is not set, then both brace escapes and
|
|
* backslash escapes are removed.
|
|
*
|
|
* Slashes (and backslashes in `windowsPathsNoEscape` mode) cannot be escaped
|
|
* or unescaped.
|
|
*/
|
|
export declare const unescape: (s: string, { windowsPathsNoEscape, }?: Pick<MinimatchOptions, "windowsPathsNoEscape">) => string;
|
|
//# sourceMappingURL=unescape.d.ts.map
|