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."
18 lines
No EOL
848 B
JavaScript
18 lines
No EOL
848 B
JavaScript
/**
|
|
* Escape all magic characters in a glob pattern.
|
|
*
|
|
* If the {@link windowsPathsNoEscape | GlobOptions.windowsPathsNoEscape}
|
|
* option is used, then characters are escaped by wrapping in `[]`, because
|
|
* a magic character wrapped in a character class can only be satisfied by
|
|
* that exact character. In this mode, `\` is _not_ escaped, because it is
|
|
* not interpreted as a magic character, but instead as a path separator.
|
|
*/
|
|
export const escape = (s, { windowsPathsNoEscape = false, } = {}) => {
|
|
// don't need to escape +@! because we escape the parens
|
|
// that make those magic, and escaping ! as [!] isn't valid,
|
|
// because [!]] is a valid glob class meaning not ']'.
|
|
return windowsPathsNoEscape
|
|
? s.replace(/[?*()[\]]/g, '[$&]')
|
|
: s.replace(/[?*()[\]\\]/g, '\\$&');
|
|
};
|
|
//# sourceMappingURL=escape.js.map
|