Add grammar/semantic tokens to all parts of feature files #299
Description
🤔 What's the problem you're trying to solve?
Keywords, values, docstrings, comments and table headers have tokens in Visual Studio Code, however all other parts of feature files do not. This is an oversight that prevents complete customisation of the styling and colours of all aspects of feature files. Without tokens, the following issues are apparent:
- Changing how feature/scenario names are displayed requires changing all other unclassified text is displayed
- There is no differentiating between feature/scenario names and supplemental information that is not a comment yet is still not executed
- All types of values are represented the same (in reference to
cucumber-js), so there is no way to differentiate between strings, integers, booleans, etc. by colour - Quote characters must have the same colour as the text they contain, there is no customising either independently
✨ What's your proposed solution?
A full pass on the tokens that this extension provides, in an attempt to line them up with established tokens for languages like Python and TypeScript.
⛏ Have you considered any alternatives or workarounds?
No response
📚 Any additional context?
Refer to bdd-power-tools, which has more comprehensive tokens.