Adding syntax highlighting #1041
Conversation
Signed-off-by: Jens Johansson <[email protected]>
Signed-off-by: Jens Johansson <[email protected]>
|
The build failed @jensakejohansson, do you have any idea why? |
Signed-off-by: Jens Johansson <[email protected]>
|
@sriv Seems it failed due to a rule in TSLint in the pipeline which doesn't apply in my local env. Changed the expression so now the linter should accept it. |
Signed-off-by: Jens Johansson <[email protected]>
|
@sriv Addad a small adjustment to also highlight concept arguments and not only arguments in steps. It was a late night yesterday, so I missed that :) Feel free to make a build when you have time... |
|
@jensakejohansson Thank you for contributing to gauge-vscode. Your pull request has been labeled as a release candidate 🎉🎉. Merging this PR will trigger a release. Please bump up the version as part of this PR.Instructions to bump the version can found at CONTRIBUTING.md If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done. |
…ge server. (#1038) * Added setting for config Gauge formatter and send the settings to Gauge server. Signed-off-by: Jens Johansson <[email protected]> * Added setting for config Gauge formatter and send the settings to Gauge server. Signed-off-by: Jens Johansson <[email protected]> * Bump @types/node from 22.10.10 to 22.13.0 (#1039) Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.10.10 to 22.13.0. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Adding syntax highlighting (#1041) * Adding code & default config syntax highlighting. Signed-off-by: Jens Johansson <[email protected]> * Adding code & default config syntax highlighting. Signed-off-by: Jens Johansson <[email protected]> * Adding code & default config syntax highlighting. Signed-off-by: Jens Johansson <[email protected]> * Adding code & default config syntax highlighting. Signed-off-by: Jens Johansson <[email protected]> --------- Signed-off-by: Jens Johansson <[email protected]> * Added setting for config Gauge formatter and send the settings to Gauge server. Signed-off-by: Jens Johansson <[email protected]> * Added setting for config Gauge formatter and send the settings to Gauge server. Signed-off-by: Jens Johansson <[email protected]> --------- Signed-off-by: Jens Johansson <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
@jensakejohansson thanks for this, it was a very welcome surprise when I was working on some specs today! |
Hi!
@sriv @zabil
Addressing this issue:
#884
Implemented syntax highlighting. All token-matching is done on extensions side. Extension provides default colors that works fine with VSC default (dark) theme, but can be overridden in settings.json.
Also, during test development I often want to temporarily disable one or multiple steps in a scenario. Although it's not technically markdown I simply put the common "//" in front of the step (and any table) and then the runner ignores it. I've added a binding to VSC short-cut for comment/un-comment that adds "//" at the beginning of the line (which makes it possible to disable many steps quickly my selecting multiple lines). I find it very convenient and I don't see that it does any harm.
Default look example:
To override any user can just set their values/colors accordingly:
