Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.12.2
->4.1.0
Release Notes
nodeca/js-yaml
v4.1.0
Compare Source
Added
yaml.types.XXX
.options
property with original arguments kept as they were(see
yaml.types.int.options
as an example).Changed
Schema.extend()
now keeps old type order in case of conflicts(e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as
abcd
instead ofcbad
).v4.0.0
Compare Source
Changed
!!js/function
,!!js/regexp
,!!js/undefined
aremoved to js-yaml-js-types package.
safe*
functions. Useload
,loadAll
,dump
instead which are all now safe by default.
yaml.DEFAULT_SAFE_SCHEMA
andyaml.DEFAULT_FULL_SCHEMA
are removed, useyaml.DEFAULT_SCHEMA
instead.yaml.Schema.create(schema, tags)
is removed, useschema.extend(tags)
instead.!!binary
now always mapped toUint8Array
on load./lib
folder.01234
is now decimal,0o1234
is octal,1:23
is parsed as string instead of base60).dump()
no longer quotes:
,[
,]
,(
,)
except when necessary, #470, #557.(X:Y)
instead ofat line X, column Y
(also present in compact format), #332.dump()
now serializesundefined
asnull
in collections and removes keys withundefined
in mappings, #571.dump()
withskipInvalid=true
now serializes invalid items in collections as null.!
are now dumped as!tag
instead of!<!tag>
, #576.tag:yaml.org,2002:
are now shorthanded using!!
, #258.Added
.mjs
(es modules) support.quotingType
andforceQuotes
options for dumper to configurestring literal style, #290, #529.
styles: { '!!null': 'empty' }
option for dumper(serializes
{ foo: null }
as "foo:
"), #570.replacer
option (similar to option in JSON.stringify), #339.Tag
can now handle all tags or multiple tags with the same prefix, #385.Fixed
dump()
, #587.[foo,,bar]
) now throw an exceptioninstead of producing null, #321.
__proto__
key no longer overrides object prototype, #164.bower.json
.load()
and url-encoded indump()
(previously usage of custom non-ascii tags may have led to invalid YAML that can't be parsed).
v3.14.1
Compare Source
Security
.load()
(in &anchor).v3.14.0
Compare Source
Changed
safe/loadAll(input, options)
variant of call.Fixed
=
in plain scalars #519.!<?>
tag in case user manually specifies it.v3.13.1
Compare Source
Security
.load()
, #480.v3.13.0
Compare Source
Security
safeLoad()
can hang when arrays with nested refsused as key. Now throws exception for nested arrays. #475.
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.