🚧 NEOS Fusion & AFX 🚧
This package is WIP
resource:// Goto Definition, Completion and Hover
It currently only workes when it is a fusion string. When the file is an image it gets preview on hover
@propTypes are now parsed as a valid property definition. So if there is no property in the prototype but one defined in
@propTypes it will be the GoTo-Target. This also affects diagnostics so less
props. will be marked as a problem.
✨ Improved Definition and Hover Capabilities
Definitions are now following inheritence and overrides. It still only works on
props. and will fail on more complex fusion as
@context is currently not resolved.
✨ Implemented basic diagnostics
It is based on the definition capability. Because the definition capability does not work perfectly in complex fusion the feature is marked as
experimental. If it bothers you too much it can be disabled in the extension configuration.
✨ Improved Description parsing
EEL-Helper descriptions should now be parsed without any problems. Things like
@params are also read but currently not processed.
Currently works on Prototypes and fusion Properties (detected by
Support for EEL-Helper is present, but currently not for functions (like
Find References (Shift + CMD + Click)
Currently works on Prototypes only.
Support for EEL as well as Fusion-Properties will be added in the future.
Currently works on Prototypes and Properties only and just shows the name and sometimes the value of the property. Will provide more information from the yaml-configuration in the future.
Support for EEL-Helper ist present but the description parsing is not working a 100% correct.
Currently works on Prototype-Names and Fusion-Properties only and it does autocomplete them on every point inside the fusion-file. Which is better than typing it by hand but still far from perfect.
Real support (not just string comparison) will be added in the not so far but still far future.
How does it work?
The language-server relies heavely on the ts-fusion-parser which is a typescript port of the "official" Fusion Parser.
Essentialy it reads all AST-Nodes from the fusion parser and checks if the curser is on one of these AST-Nodes. If it is, the relevant actions are carried out.
The AFX and EEL parser is part of the ts-fusion-parser.
Is there a roadmap?
Currently there is no roadmap.
What about EEL-Helper and NodeType-Configuration
There is rudimentary support for EEL-Helper. Hover and Goto-Definition is currently (somewhat) supported.
- EEL-Helper hover description will parse the first description it can find which may not be the correct one
- EEL-Helper with the same name may be handled incorrectly
- Autocompletion is just a list with no semantic meaning