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
1 KiB
JSON
18 lines
1 KiB
JSON
[
|
|
{
|
|
"name": "html",
|
|
"description": "Outputs results to HTML. The `html` formatter is useful for visual presentation in the browser."
|
|
},
|
|
{
|
|
"name": "json-with-metadata",
|
|
"description": "Outputs JSON-serialized results. The `json-with-metadata` provides the same linting results as the [`json`](#json) formatter with additional metadata about the rules applied. The linting results are included in the `results` property and the rules metadata is included in the `metadata` property.\n\nAlternatively, you can use the [ESLint Node.js API](../../integrate/nodejs-api) to programmatically use ESLint."
|
|
},
|
|
{
|
|
"name": "json",
|
|
"description": "Outputs JSON-serialized results. The `json` formatter is useful when you want to programmatically work with the CLI's linting results.\n\nAlternatively, you can use the [ESLint Node.js API](../../integrate/nodejs-api) to programmatically use ESLint."
|
|
},
|
|
{
|
|
"name": "stylish",
|
|
"description": "Human-readable output format. This is the default formatter."
|
|
}
|
|
]
|