Skip to content

Add languages yaml-textmate & yaml-tmlanguage#1093

Merged
datho7561 merged 5 commits intoredhat-developer:mainfrom
RedCMD:patch-1
Oct 1, 2025
Merged

Add languages yaml-textmate & yaml-tmlanguage#1093
datho7561 merged 5 commits intoredhat-developer:mainfrom
RedCMD:patch-1

Conversation

@RedCMD
Copy link
Contributor

@RedCMD RedCMD commented Feb 9, 2025

Fixes #1092

I could add them to "activationEvents" as well
but the 3rd party extensions can activate this one instead via "extensionDependencies"

vscode-yaml/package.json

Lines 41 to 44 in e696d9b

"activationEvents": [
"onLanguage:yaml",
"onLanguage:dockercompose"
],


also I think *.y(a)ml is a invalid glob pattern

documentSelector: [{ language: 'yaml' }, { language: 'dockercompose' }, { pattern: '*.y(a)ml' }],

Copy link
Contributor

@msivasubramaniaan msivasubramaniaan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update it on

vscode-yaml/package.json

Lines 41 to 44 in e696d9b

"activationEvents": [
"onLanguage:yaml",
"onLanguage:dockercompose"
],
as well

@RedCMD
Copy link
Contributor Author

RedCMD commented Mar 11, 2025

@msivasubramaniaan done thanks

@msivasubramaniaan
Copy link
Contributor

@RedCMD Please resolve the conflicts. Thanks

RedCMD added a commit to RedCMD/TmLanguage-Syntax-Highlighter that referenced this pull request Mar 16, 2025
@RedCMD
Copy link
Contributor Author

RedCMD commented Mar 19, 2025

@msivasubramaniaan done

@carlwr
Copy link

carlwr commented May 25, 2025

Just want to chime in - this would be a great thing to have. Hoping this can be merged. :D

@datho7561
Copy link
Contributor

Yeah, the pattern is wrong :(

I think this also need to be done on the language server side (https://github.com/redhat-developer/yaml-language-server). See redhat-developer/yaml-language-server@6424ff6 for an example.

Copy link
Contributor

@datho7561 datho7561 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RedCMD I think this would be good change to merge. Do you mind rebasing to resolve the merge conflicts?

@RedCMD
Copy link
Contributor Author

RedCMD commented Oct 1, 2025

@datho7561 thank you
I'm not seeing any merge conflicts

here's the server side pr:

Copy link
Contributor

@datho7561 datho7561 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I can confirm files like JavaScript-NEXT.YAML-tmLanguage activate the extension. With redhat-developer/yaml-language-server#1132, you can also format these files.

@datho7561 datho7561 merged commit b306979 into redhat-developer:main Oct 1, 2025
1 of 3 checks passed
datho7561 pushed a commit to redhat-developer/yaml-language-server that referenced this pull request Oct 1, 2025
phunguyenmurcul added a commit to macrosreply/yaml-language-server that referenced this pull request Oct 3, 2025
* checked const value for the boolean type

* test case added

* added positive test case as well

* Fix corner case for 'flow sequence forbidden' quickfix

- Do not include any trailing spaces in the error range
  - This is a change in behaviour; it seems this behaviour was
    intentional based on the test cases,
    but I don't agree with it, since the error range should only cover
    the erroneous code.
- Fix a bug where `]` or `}` are not included in the error range if they're the last character in the document

Fixes redhat-developer#1060

Signed-off-by: David Thompson <davthomp@redhat.com>

* added dockercompose and github actions in setting handler

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* Fix YAML JSON Schema files starting with %YAML 1.x

Fix a bug where YAML files containing a JSON Schema that start with
%YAML 1.x or a comment that contains a number would fail to to be parsed.

This is caused by the fact that the JSON Schema parser would contain the
number, e.g. 1.2 as the value of `unresolvedJsonSchema.schema` and so
the test for `=== undefined` would fail. This would cause the error from
the JSON parser to be returned instead of trying to parse the file as a
YAML file.

To work around this, also check if `unresolvedJsonSchema.schema` is a
number. It if is, it clearly was not a JSON Schema and so we can safely
try to parse the file as a YAML file.

Fixes: redhat-developer#922
Signed-off-by: David Lechner <dlechner@baylibre.com>

* show the matching value on top

* fix eslint issue

* removed enumMarkdown entries

* Fix bool enums (redhat-developer#1080)

* add (failing) test case for boolean enum and const values

failing with:

```
[
  {
    code: 1,
    data: {
      schemaUri: [ 'file:///default_schema_id.yaml' ],
      values: [ true, false ]
    },
    message: 'Value is not accepted. Valid values: true, false.',
    range: {
      end: { character: 15, line: 0 },
      start: { character: 11, line: 0 }
    },
    severity: 1,
    source: 'yaml-schema: file:///default_schema_id.yaml'
  }
]
```

* fix the issue for `boolean` values in `enum`

this is the same fix for `enum` that has been applied a while back for `const` values here: redhat-developer@e6165e4

fixes issue: redhat-developer#1078

---------

Co-authored-by: xxx <xxx>

* Support draft-04 schemas (redhat-developer#1065)

This helps to support the schema for openapi 3.0.0,
among others, that use an older draft of JSON schema that has some type
differences that make it incompatible with JSON schema draft 07.

See redhat-developer#1006 , I think the root cause for the issues that PR caused
is that we were trying to download and cache the metaschema from
the "URL" instead of using the copy that's bundled with `ajv`.

Fixes redhat-developer#780, Fixes redhat-developer#752

(and many, many duplicates we'll have to find and clean up)

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix recursion bug in ast-conversion (redhat-developer#1076)

* Ensure recursion works as expected

* fix test safety for when parse fails

* use a cache to keep track of resolved aliases

* Added l10n bundle for various language and translate the local strings (redhat-developer#1086)

* added l10n bundle for various language and translate the local strings

* upstream node

* upstream node

* update to node 18

* Changed NodeJS.Timeout as per node 18

* upstream to node 20

* updated coversall script

* fixed test case

* override json service translation

* fixed test cases

* fix/improve enum value descriptions for merged enum lists (redhat-developer#1085)

This is a follow-up submission for redhat-developer#1028, which removes duplicate enum values in merged enum lists.

This fix/improvement ensures that the first **non-empty** enum description is used for the corresponding enum value.

Before this fix: if the first non-unique enum value was not providing a description but the second one was, it was not
picked up and the enum value description stayed empty.

Co-authored-by: xxx <xxx>
Co-authored-by: Muthurajan Sivasubramanian <93245779+msivasubramaniaan@users.noreply.github.com>

* added test cases for bundle and configuration through testhelper class

* Fix array of const completion

* Fix ignoreScalar in value completion

* apply patch

* Updated changelog for the release 1.19.0 (redhat-developer#1094)

* Updated changelog for the release 1.19.0

* updated chhangelog.md

* addressed review comments

* @vscode/l10n is a runtime dependency (redhat-developer#1096)

* check NODE_AUTH_TOKEN is available or not (redhat-developer#1098)

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* Fix auth on npm publish (redhat-developer#1099)

* check NODE_AUTH_TOKEN is available or not

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* set NODE_AUTH_TOKEN

---------

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* Fix auth on npm publish (redhat-developer#1100)

* check NODE_AUTH_TOKEN is available or not

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* set NODE_AUTH_TOKEN

* set npmAuthToken $NODE_AUTH_TOKEN

* set npmAuthToken $NODE_AUTH_TOKEN

---------

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* Update CI.yaml (redhat-developer#1101)

just set token to 123 and check what error occur

* Revert "Update CI.yaml (redhat-developer#1101)" (redhat-developer#1102)

This reverts commit 8c4c22f.

* Fix auth on npm publish (redhat-developer#1103)

* check NODE_AUTH_TOKEN is available or not

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* set NODE_AUTH_TOKEN

* set npmAuthToken $NODE_AUTH_TOKEN

* set npmAuthToken $NODE_AUTH_TOKEN

* all the required parameters are set

---------

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* Fix the fallback path to the l10n folder (redhat-developer#1104)

If the language server client doesn't specify the location of the l10n
folder, then the language server falls back to a path relative to the
complied file.
This path was wrong; `server.js` is in `./out/server/src/server.js`,
so the relative path of the `l10n` folder is `../../../l10n` instead of
`../l10n`.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix the fallback path to the l10n folder (redhat-developer#1104) (redhat-developer#1105)

If the language server client doesn't specify the location of the l10n
folder, then the language server falls back to a path relative to the
complied file.
This path was wrong; `server.js` is in `./out/server/src/server.js`,
so the relative path of the `l10n` folder is `../../../l10n` instead of
`../l10n`.

Signed-off-by: David Thompson <davthomp@redhat.com>
Co-authored-by: David Thompson <davidethompson@me.com>

* Fix NPM broken (redhat-developer#1095)

* set always-auth true

* added registry url and release ci on main push for testing

* removed main push

* renamed to NPM_TOKEN

* used YARN_NPM_AUTH_TOKEN

* used npm_token

* used YARN_NPM_AUTH_TOKEN

* added registry-url

* tried NODE_AUTH_TOKEN

* created .npmrc file

* removed .npmrc

* check NODE_AUTH_TOKEN available or not

* moved the check code on top

* checked NPM_TOKEN

* tried with NODE_AUTH_TOKEN

* Try with NPM instead of YARN

* switch to npm

* removed install command

* fix build issue

* fix build issue

* done pkg fix

* Completely moved to npm from yarn

* review comments addressed

* Bump serialize-javascript and mocha

Bumps [serialize-javascript](https://github.com/yahoo/serialize-javascript) to 6.0.2 and updates ancestor dependency [mocha](https://github.com/mochajs/mocha). These dependencies need to be updated together.


Updates `serialize-javascript` from 6.0.0 to 6.0.2
- [Release notes](https://github.com/yahoo/serialize-javascript/releases)
- [Commits](yahoo/serialize-javascript@v6.0.0...v6.0.2)

Updates `mocha` from 9.2.2 to 11.7.1
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md)
- [Commits](mochajs/mocha@v9.2.2...v11.7.1)

---
updated-dependencies:
- dependency-name: serialize-javascript
  dependency-version: 6.0.2
  dependency-type: indirect
- dependency-name: mocha
  dependency-version: 11.7.1
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

* Remove coveralls dependency (redhat-developer#1107)

From my understanding, I think we just need the GitHub Action in order
for things to work.

Signed-off-by: David Thompson <davthomp@redhat.com>

* set .npmrc (redhat-developer#1109)

* add encoding dependency

* upstream @vsode/l10n dependency

* updated changelog.md (redhat-developer#1111)

* Fixed broken link to JSON schema website

* Fix release GitHub Action

- setup-node@v5 creates a .npmrc if you provide a registry,
  so there should be no need to do that separately
- after setup-node@v5 is run, `npm publish` expects the token to be
  accessible from the environment variable `NODE_AUTH_TOKEN`
- also fix coveralls, because that's getting annoying
  (root cause is that it tried to publish the results for each platform
  instead of just once)

See https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#publish-to-npmjs-and-gpr-with-npm

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix prerelease publishing

The options that were being used in `npm publish` to modify the version
to include the git hash at the end are intended to be used
with the `npm version` command beforehand instead.
I think this got messed up somewhere along the way while rewriting the
GitHub Action.

Fixes redhat-developer#1128

Signed-off-by: David Thompson <davthomp@redhat.com>

* Upversion to 1.19.1

We burned the 1.19.0 release by publishing a prerelease version labelled
1.19.0. In order to release, we'll need to use a different version
number.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Upversion to 1.20.0

* remove \n in README (redhat-developer#1068)

fix typo

Signed-off-by: roc <roc@imroc.cc>
Co-authored-by: David Lechner <david@lechnology.com>

* Wrapping code action title with string (redhat-developer#1117)

* Wrapping code action title with string

* adding textedit value field wrapped as string

* README.md: Mention kate as a Client

The `kate` editor has `yaml-language-server` as its default for the YAML format built-in (no plugins or manual configuration needed).

* Support `yaml-textmate` and `yaml-tmlanguage` languages

* redhat-developer/vscode-yaml#1093

* fix: cast cleanupInterval to any before clearing interval

* fix: remove max-warnings option from lint scripts for better flexibility

* Remove @microsoft/eslint-formatter-sarif from devDependencies in package.json

---------

Signed-off-by: David Thompson <davthomp@redhat.com>
Signed-off-by: msivasubramaniaan <msivasub@redhat.com>
Signed-off-by: David Lechner <dlechner@baylibre.com>
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: roc <roc@imroc.cc>
Co-authored-by: msivasubramaniaan <msivasub@redhat.com>
Co-authored-by: David Thompson <davthomp@redhat.com>
Co-authored-by: David Lechner <dlechner@baylibre.com>
Co-authored-by: Kosta <2526664+Kosta-Github@users.noreply.github.com>
Co-authored-by: David Thompson <davidethompson@me.com>
Co-authored-by: pjsk-stripe <55514208+pjsk-stripe@users.noreply.github.com>
Co-authored-by: Muthurajan Sivasubramanian <93245779+msivasubramaniaan@users.noreply.github.com>
Co-authored-by: ShadiestGoat <48590492+ShadiestGoat@users.noreply.github.com>
Co-authored-by: Daniel M. Capella <polyzen@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: debbie <148627186+webdevred@users.noreply.github.com>
Co-authored-by: roc <roc@imroc.cc>
Co-authored-by: David Lechner <david@lechnology.com>
Co-authored-by: Arunvenmany <arun.kumar.v.n@ibm.com>
Co-authored-by: Niels Thykier <niels@thykier.net>
Co-authored-by: RedCMD <33529441+RedCMD@users.noreply.github.com>
phunguyenmurcul added a commit to macrosreply/vscode-yaml that referenced this pull request Mar 9, 2026
* updated eslint version

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* changelog updated for the release v1.17.0

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* add language 'github-actions-workflow'

* bumped v1.18.0

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* updated chagelog for the release 1.18.0

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* bump version 1.19.0

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* Fix build failure due to prettier error

Fixes redhat-developer#1117

Signed-off-by: David Thompson <davthomp@redhat.com>

* Stabilize UI tests

This PR uses delays in order to get the "YAML custom tags works as expected"
test passing consistently.

My best guess as to why this works is that it takes bit of time
for the setting change to propagate to the language server.

Fixes redhat-developer#1119

Signed-off-by: David Thompson <davthomp@redhat.com>

* Add formatting option for trailing comma

See redhat-developer/yaml-language-server#1063, this PR requires that
PR in order to work.

Fixes redhat-developer#1112

Signed-off-by: David Thompson <davthomp@redhat.com>

* update settings.json as default formatter as yaml

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>

* send vscode configured language to LS

* upstream node

* handled locale on YAML LS side

* removed yarn dependency and added npm

* fixed build issue

* removed .yarnrc

* check yarn availability

* removed yarn

* removed yarn completely

* removed yarn.lock

* check yarn

* removed the yarn

* add -force instead of -f

* removed yarn based on OS

* fix winows CI build issue

* removed -y(yarn) in the script

* CHANGELOG for 1.19.0

Signed-off-by: David Thompson <davthomp@redhat.com>

* l10n missing from .vsix

1. The `l10n` folder, which contains all the translations, was not
   present anywhere in the built .vsix. The translations are required in
   order to run yaml-language-server, so I copied from
   yaml-language-server to `dist/l10n`.
2. The location of l10n was listed as `../yaml-language-server/l10n`.
   This doesn't work if yaml-language-server isn't cloned locally,
   and doesn't work when running as a .vsix, so I changed it to
   `./dist/l10n`.
3. During the CI run, npm isn't installing the latest prerelease of
   yaml-language-server. I added a step to force it to use the latest
   yaml-language-server. This is important, because the above bugs
   could have been caught earlier if we were actually testing against
   the newest yaml-language-server.

Fixes redhat-developer#1152

Signed-off-by: David Thompson <davthomp@redhat.com>

* Upversion to 1.20.0

* Publish prereleases

Fixes redhat-developer#1155

Signed-off-by: David Thompson <davthomp@redhat.com>

* Revert "update settings.json as default formatter as yaml"

This reverts commit 84d4516.

Fixes redhat-developer#1157

Adjusting the user settings automatically was annoying to some users.
The main bug fix, which consisted of setting the document selector to
include Docker Compose and GitHub Action files,
will not be reverted.

* Fix prerelease GitHub Action

I had the wrong path for the script to bump the version.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Don't tag prereleases

Fixes redhat-developer#1162

Signed-off-by: David Thompson <davthomp@redhat.com>

* Add languages `yaml-textmate` & `yaml-tmlanguage` (redhat-developer#1093)

* Add languages `yaml-textmate` & `yaml-tmlanguage`

* Add to `activationEvents`

* Fix scheduled prerelease skipping publish step

The prerelease build skipped the publishing step.
(See
https://github.com/redhat-developer/vscode-yaml/actions/runs/18187139533/job/51773763520)

This should prevent the publishing step from being skipped.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Another fix for prereleases

In order to skip tagging the prerelease version,
we need to entirely skip the publish to GitHub Releases step.
Passing a null tag causes the step to error,
which ends the build.

Signed-off-by: David Thompson <davthomp@redhat.com>

* CHANGELOG for 1.19.1

Signed-off-by: David Thompson <davthomp@redhat.com>

* Upversion to 1.20.0

Signed-off-by: David Thompson <davthomp@redhat.com>

* feat: Register `ansible` and `ansible-jinja` languages for formatter (redhat-developer#1179)

* feat: Register `ansible` and `ansible-jinja` languages for formatter

* docs: Add changelog after getting issue number

* refactor: Change yaml pattern and release tag to follow upstream

* docs: Remove version entry in changelog

* docs: Improve changelog

* docs: Clear update entry

* Don't syntax highlight `1.4.0` as a float

Modify the TextMate grammar so that it doesn't count `1.4.0` as a floating point number.
The current regular expression was taken from the YAML 1.1 spec,
but the regular expression contradicts the examples and explanation and
was likely an error.
The new regular expression was taken from the YAML 1.2.2 spec.
Notably, I believe that `1.4.0` is treated as a string in 1.1 and 1.2 YAML deserializers.

It doesn't seem like we'll be able to upstream this change into TextMate,
given there's an existing upstream PR to make this change that hasn't been
merged.

Fixes redhat-developer#901

Signed-off-by: David Thompson <davthomp@redhat.com>

* Update CODEOWNERS

Muthu is working on other tasks and unfortunately doesn't have time to
work on yaml-language-server.
For the time being, I've been handling PR reviews and managing issues.
Updating the CODEOWNERS to reflect this will automatically
request for me to review any new PRs that come in,
and will skip pinging Muthu.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix macOS CI UI tests (redhat-developer#1186)

* await for progress bar to disappear

* Update customTagsTest.ts

* Update extensionUITest.ts

* Update extensionUITest.ts

* Update extensionUITest.ts

* Update extensionUITest.ts

* Update extensionUITest.ts

* increase timeout

* Update extensionUITest.ts

* Improve documentation for the `yaml.schemas` setting

Fixes redhat-developer#1147

Signed-off-by: David Thompson <davthomp@redhat.com>

* Settings for "auto-detect Kubernetes crd schema" (redhat-developer#1192)

* Settings for "auto-detect Kubernetes crd schema"

See redhat-developer/yaml-language-server#1050

Settings to enable/disable the feature and change the repository used to
find CRD schemas.

Use
https://raw.githubusercontent.com/nlamirault/crd-schema-store/refs/heads/main/schemas
to test an alternate store of CRD schemas.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix wording of enable setting

Co-authored-by: Morgan Chang <shin19991207@gmail.com>

* Fix wording of url setting

Co-authored-by: Morgan Chang <shin19991207@gmail.com>

* Add a quote that somehow got lost

Signed-off-by: David Thompson <davthomp@redhat.com>

---------

Signed-off-by: David Thompson <davthomp@redhat.com>
Co-authored-by: Morgan Chang <shin19991207@gmail.com>

* Add new setting to enable/disable anchor hover support

See redhat-developer/yaml-language-server#1150

Draft PR until it gets merged.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix running as a web extension, add smoke tests to prevent another regression (redhat-developer#1193)

* On web, send a message to the worker containing the translations

Translations weren't working at all when running the language server in
a web worker. In fact, the server was crashing immediately,
since the server was trying to load them from the filesystem.

This PR provides the translations to the server using the webworker
message passing mechanism.

Requires redhat-developer/yaml-language-server#1165

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix web support, add smoke tests

1. Fix schema content resolving when running on web
   (referencing a schema with a relative path wasn't working)
2. Add smoke tests for desktop using `@vscode/test-cli`
3. Add smoke tests for web using `@vscode/test-web`

The smoke tests are very minimal; it loads a YAML file that references a
schema using a relative path and verifies the expected diagnostics
appear.

Signed-off-by: David Thompson <davthomp@redhat.com>

---------

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix resolving schema content on web

Use a new extension point, which requests schema content by URI instead
of filepath.
This is helpful, since web instances may use URIs with schemas other
than `file://` to refer to the files in the workspace.

Add a smoke test.

Fixes redhat-developer#1194

Signed-off-by: David Thompson <davthomp@redhat.com>

* Remove debug notification

Missed removing it before I pushed the code,
and it unfortunately got missed in review too.

Signed-off-by: David Thompson <davthomp@redhat.com>

* CHANGELOG for 1.20.0

Signed-off-by: David Thompson <davthomp@redhat.com>

* Upversion to 1.21.0

Signed-off-by: David Thompson <davthomp@redhat.com>

* Switch to 1.20.1

Given we're doing a release to address bugs introduced in 1.20.1,
I think that we should mark the nexte version as a patch release.

Signed-off-by: David Thompson <davthomp@redhat.com>

* Fix documentation of `yaml.schemas` setting

You can use a single glob or an array of globs.
I've updated the documentation and JSON Schema to reflect this.

Fixes redhat-developer#1207

Signed-off-by: David Thompson <davthomp@redhat.com>

* Replaced the asterisk based file matching with explicit YAML language IDs (redhat-developer#1209)

* replaced the asterisk based file matching with explicit YAML language IDs

Signed-off-by: Morgan Chang <shin19991207@gmail.com>

* remove unsupported language IDs

Signed-off-by: Morgan Chang <shin19991207@gmail.com>

---------

Signed-off-by: Morgan Chang <shin19991207@gmail.com>

* make yaml.validate and yaml.format.enable language overridable

Signed-off-by: Morgan Chang <shin19991207@gmail.com>

* switch back to 1.21.0

* Add yaml-lint-disable comment to suppress diagnostics per-line

Add support for suppressing linter diagnostics on a per-line basis using a yaml-lint-disable comment placed on the line immediately before the one producing the diagnostic.

The comment supports three forms: suppress all diagnostics, suppress by message substring, or suppress by multiple comma-separated substrings (case-insensitive). Implemented via LSP client middleware that intercepts diagnostics from the yaml-language-server and filters out suppressed ones before they reach VS Code.

Co-authored-by: Cursor <cursoragent@cursor.com>

* Refine tests and JSDocs

* Remove code

* Rename yaml-lint-disable to yaml-language-server-disable

* CHANGELOG for 1.21.0 (redhat-developer#1215)

Signed-off-by: David Thompson <davthomp@redhat.com>
Co-authored-by: Morgan Chang <shin19991207@gmail.com>

* Upversion to 1.22.0

Signed-off-by: David Thompson <davthomp@redhat.com>

* feat(yaml): add YAML language service features

- Implemented YamlLinks service for finding document links in YAML files.
- Added YamlOnTypeFormatting service for handling on-the-fly formatting in YAML.
- Created YamlRename service to support renaming anchors in YAML documents.
- Introduced YamlSelectionRanges service to provide selection ranges for YAML nodes.
- Enhanced YamlSchemaService with new schema modification actions.
- Added diagnostic filtering capabilities for suppressing specific diagnostics in YAML.
- Implemented utility functions for handling YAML AST and scalar types.
- Updated telemetry interface for error reporting.
- Refactored text buffer utilities for better line handling.
- Updated Kubernetes schema URL to the latest version.
- Adjusted schema status bar item to work with eBuilder YAML language.

* fix: outdate config

* feat: add support for .eyaml and .eyml file extensions

---------

Signed-off-by: msivasubramaniaan <msivasub@redhat.com>
Signed-off-by: David Thompson <davthomp@redhat.com>
Signed-off-by: Morgan Chang <shin19991207@gmail.com>
Co-authored-by: msivasubramaniaan <msivasub@redhat.com>
Co-authored-by: Muthurajan Sivasubramanian <93245779+msivasubramaniaan@users.noreply.github.com>
Co-authored-by: Alberto Cavalcante <54247214+albertocavalcante@users.noreply.github.com>
Co-authored-by: David Thompson <davthomp@redhat.com>
Co-authored-by: RedCMD <33529441+RedCMD@users.noreply.github.com>
Co-authored-by: Lanqing Huang <lqhuang@outlook.com>
Co-authored-by: Morgan Chang <shin19991207@gmail.com>
Co-authored-by: Simon Heather <simon.heather@yulife.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support YAML TextMate files

4 participants