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."
27 lines
932 B
JavaScript
27 lines
932 B
JavaScript
"use strict";
|
|
|
|
module.exports = function ({ plugins }) {
|
|
const isArrayOfStrings = typeof plugins[0] === "string";
|
|
|
|
return `
|
|
A config object has a "plugins" key defined as an array${isArrayOfStrings ? " of strings" : ""}. It looks something like this:
|
|
|
|
{
|
|
"plugins": ${JSON.stringify(plugins)}
|
|
}
|
|
|
|
Flat config requires "plugins" to be an object, like this:
|
|
|
|
{
|
|
plugins: {
|
|
${isArrayOfStrings && plugins[0] ? plugins[0] : "namespace"}: pluginObject
|
|
}
|
|
}
|
|
|
|
Please see the following page for information on how to convert your config object into the correct format:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#importing-plugins-and-custom-parsers
|
|
|
|
If you're using a shareable config that you cannot rewrite in flat config format, then use the compatibility utility:
|
|
https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config
|
|
`;
|
|
};
|