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."
36 lines
807 B
TypeScript
36 lines
807 B
TypeScript
declare namespace stripJsonComments {
|
|
interface Options {
|
|
/**
|
|
Replace comments with whitespace instead of stripping them entirely.
|
|
|
|
@default true
|
|
*/
|
|
readonly whitespace?: boolean;
|
|
}
|
|
}
|
|
|
|
/**
|
|
Strip comments from JSON. Lets you use comments in your JSON files!
|
|
|
|
It will replace single-line comments `//` and multi-line comments `/**\/` with whitespace. This allows JSON error positions to remain as close as possible to the original source.
|
|
|
|
@param jsonString - Accepts a string with JSON.
|
|
@returns A JSON string without comments.
|
|
|
|
@example
|
|
```
|
|
const json = `{
|
|
// Rainbows
|
|
"unicorn": "cake"
|
|
}`;
|
|
|
|
JSON.parse(stripJsonComments(json));
|
|
//=> {unicorn: 'cake'}
|
|
```
|
|
*/
|
|
declare function stripJsonComments(
|
|
jsonString: string,
|
|
options?: stripJsonComments.Options
|
|
): string;
|
|
|
|
export = stripJsonComments;
|