How femadevspace/femascript-lang works
FemaScript Lang is a Visual Studio Code language-support extension for an educational Portugol-inspired language. The principal workflow is an editor document entering the extension, being parsed for syntax feedback or formatted into a text edit. The grammar spans lexing and parsing; formatting uses a CST visitor and style rules. The README also documents syntax highlighting and snippets, but the supplied tree shows no snippets implementation. Edges are limited to relationships visible in excerpts, the source index, or README; unsampled internals are not assumed.
Main entry points: formatting.ts Format provider · semantics.ts Syntax checking · formatter-helper.ts Format engine · index.ts Feature registry
Components 20
Editor integration
- Extension entry
src/extension.ts - Feature registry
src/features/index.ts - Diagnostics
src/features/diagnostics.ts - Syntax checking
src/features/semantics.ts - Format provider
src/features/formatting.ts - Syntax highlighting
src/utils/textmate.ts
Language grammar
- Grammar exports
src/grammar/index.ts - Lexer
src/grammar/lexer/lexer.ts - Token definitions
src/grammar/lexer/tokens/keywords.ts - Parser
src/grammar/parser/parser.ts
Formatting
- Format engine
src/formatter/formatter-helper.ts - CST visitor
src/formatter/formatter.ts - Control-flow visitors
src/formatter/visitors/statements-control-flow.ts - Layout rules
src/formatter/rules/breaklines.ts - Format settings
src/formatter/settings.ts - Rule helpers
src/formatter/utils/rules.ts
Shared utilities
- Comment processing
src/utils/comments/index.ts - Language globals
src/utils/globals.ts - Safe results
src/utils/safe.ts
Other components
- VS Code
Connections 27
- VS Code → Extension entry: activates
- Extension entry → Feature registry: registers
src/extension.ts - Feature registry → Diagnostics: registers
src/features/index.ts - Feature registry → Format provider: registers
src/features/index.ts - Feature registry → Syntax checking: registers
src/features/index.ts - VS Code → Format provider: requests formatting
src/features/formatting.ts - Format provider → Format engine: formats text
src/features/formatting.ts - Format provider → Format settings: loads defaults
src/features/formatting.ts - Syntax checking → Grammar exports: parses input
src/features/semantics.ts - Syntax checking → Diagnostics: reports errors
src/features/semantics.ts - Syntax checking → Language globals: uses language ID
src/features/semantics.ts - Syntax checking → Safe results: checks result
src/features/semantics.ts - Grammar exports → Lexer: exports
src/grammar/index.ts - Grammar exports → Parser: exports
src/grammar/index.ts - Parser → Lexer: gets tokens
src/grammar/parser/parser.ts - Parser → Token definitions: consumes tokens
src/grammar/parser/parser.ts - Parser → Comment processing: uses comment types
src/grammar/parser/parser.ts - Format engine → Grammar exports: parses input
src/formatter/formatter-helper.ts - Format engine → CST visitor: visits CST
src/formatter/formatter-helper.ts - Format engine → Format settings: applies defaults
src/formatter/formatter-helper.ts - Format engine → Rule helpers: flattens rules
src/formatter/formatter-helper.ts - CST visitor → Comment processing: prints comments
src/formatter/formatter.ts - Control-flow visitors → Layout rules: uses layout rules
src/formatter/visitors/statements-control-flow.ts - Control-flow visitors → Rule helpers: separates rules
src/formatter/visitors/statements-control-flow.ts - Format provider → Language globals: uses language ID
src/features/formatting.ts - Format provider → Safe results: checks result
src/features/formatting.ts - VS Code → Syntax highlighting: uses highlighting
README.md