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."
14 lines
No EOL
760 B
TypeScript
14 lines
No EOL
760 B
TypeScript
import { GlobOptions } from './glob.js';
|
|
/**
|
|
* Return true if the patterns provided contain any magic glob characters,
|
|
* given the options provided.
|
|
*
|
|
* Brace expansion is not considered "magic" unless the `magicalBraces` option
|
|
* is set, as brace expansion just turns one string into an array of strings.
|
|
* So a pattern like `'x{a,b}y'` would return `false`, because `'xay'` and
|
|
* `'xby'` both do not contain any magic glob characters, and it's treated the
|
|
* same as if you had called it on `['xay', 'xby']`. When `magicalBraces:true`
|
|
* is in the options, brace expansion _is_ treated as a pattern having magic.
|
|
*/
|
|
export declare const hasMagic: (pattern: string | string[], options?: GlobOptions) => boolean;
|
|
//# sourceMappingURL=has-magic.d.ts.map
|