fix: migrate to js-yaml v5#2908
Conversation
🦋 Changeset detectedLatest commit: a078710 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
|
📦 A new experimental 🧪 version v0.0.0-snapshot.1782145948 of Redocly CLI has been published for testing. Install with NPM: npm install @redocly/cli@0.0.0-snapshot.1782145948 |
| }, | ||
| ], | ||
| "message": "Can't resolve $ref: unexpected end of the stream within a single quoted scalar in "fixtures/invalid-yaml.yaml" (2:1)", | ||
| "message": "Can't resolve $ref: unexpected end of the stream within a single quoted scalar in "fixtures/invalid-yaml.yaml" (1:8)", |
There was a problem hiding this comment.
Please test this in the VSCE.
2639e3f to
8ed7d77
Compare
|
Performance Benchmark fails due to indentation, already notified the OAS description owners. |
|
📦 A new experimental 🧪 version v0.0.0-snapshot.1782209756 of Redocly CLI has been published for testing. Install with NPM: npm install @redocly/cli@0.0.0-snapshot.1782209756 |
What/Why/How?
Upgraded
js-yamlfrom v4 to v5. This fixes bundling of strings that look like numbers with underscores (e.g.'12_34'): they are now kept quoted in YAML output instead of being emitted unquoted and read back as numbers by YAML 1.1 parsers.Breaking change: js-yaml v5 parses YAML more strictly. A multi-line flow collection whose closing bracket is indented to (or below) the level of its parent key is now a parse error. For example, this no longer parses and must be reindented:
All other scalar resolution (hex/octal/leading-zero integers, capitalized booleans,
~as null, dates kept as strings) and the handling of empty/comment-only documents are unchanged.Reference
#2906
Alternative
#2907
Testing
Screenshots (optional)
Check yourself
Security