ifc-language-server/node_modules/eslint/lib/rules/no-octal-escape.js
Ryan Schultz 8afacf268a Implemented a working Language Server Protocol (LSP) for IFC files with:
- 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."
2025-12-07 10:20:07 -06:00

53 lines
1.1 KiB
JavaScript

/**
* @fileoverview Rule to flag octal escape sequences in string literals.
* @author Ian Christian Myers
*/
"use strict";
//------------------------------------------------------------------------------
// Rule Definition
//------------------------------------------------------------------------------
/** @type {import('../types').Rule.RuleModule} */
module.exports = {
meta: {
type: "suggestion",
docs: {
description: "Disallow octal escape sequences in string literals",
recommended: false,
url: "https://eslint.org/docs/latest/rules/no-octal-escape",
},
schema: [],
messages: {
octalEscapeSequence:
"Don't use octal: '\\{{sequence}}'. Use '\\u....' instead.",
},
},
create(context) {
return {
Literal(node) {
if (typeof node.value !== "string") {
return;
}
// \0 represents a valid NULL character if it isn't followed by a digit.
const match = node.raw.match(
/^(?:[^\\]|\\.)*?\\([0-3][0-7]{1,2}|[4-7][0-7]|0(?=[89])|[1-7])/su,
);
if (match) {
context.report({
node,
messageId: "octalEscapeSequence",
data: { sequence: match[1] },
});
}
},
};
},
};