Update dependency YamlDotNet to v11 #176
Merged
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:
6.1.2
->11.2.1
Release Notes
aaubry/YamlDotNet
v11.2.1
Fixes #360
v11.2.0
New features
DefaultValuesHandling
.v11.1.1
Bugfixes
There was a problem deserializing nullable enums that was introduced with release 9.1.0.
v11.1.0
New features
This allows to register a concrete class for a given interface. When deserializing a value of that interface type, the concrete class will be deserialized instead.
Other fixes
v11.0.1
Bugfixes
#596 Merge sequence of anchors in reverse order (fixes #594)
When merging sequences, the order was incorrect.
This is a breaking change. If you relied on the previous behaviour, you will need to adapt your code.
#563 Fix imutable pattern in
EmitterSettings.SkipAnchorName
.v10.1.0
The
YamlMember
attribute now has aDescription
property. When set, a comment is emitted when serializing that property:This is the age
Age: 100
male or female
Sex: male
v10.0.0
New features
list:
- item1
- item2
By using this option, the emitter will output:
list:
- item1
- item2
Bug fixes
AnchorNotFoundException
if there is a reference to an anchor of a node which is being deserialized. This happens in cyclic references.Other changes
Breaking - Binary serialization support has been removed as there was no practical use-case for it.
Refactor
Portability.cs
into conditionally included files to improve maintainability.There is now a set of directories under
YamlDotNet/Helpers/Portability
. Each directory's name contains a list of target platforms, separated by+
. Each of those files is included only when building for one of those target platforms. Each directory may also contain a subsirectory namedothers
. The files in this directory are included only when building for one target platform that is not in it's parent name.Make the type Nothing a ValueType
There's no need for it to be a reference type.
Use a custom type to represent anchor names
This enables the compiler to detect when we pass something else
where an anchor name is expected.
Use a custom type to represent tag names
This enables the compiler to detect when we pass something else
where a tag name is expected.
Release notes are no longer stored in the repository, because this forced a new meaningless commit to be created for each release.
v9.1.4
v9.1.3
Fixes #560
v9.1.2
This fixes another critical bug that was causing failures while parsing Yaml documents. If you are using release 9.1.1, please use this version instead.
v9.1.1
This fixes a critical bug that was causing failures while parsing Yaml documents. If you are using release 9.1.0, please use this version instead.
v9.1.0
Improvements
Bugfixes
YamlMappingNode will now return the items in the order they appear inside the document.
v8.1.2
Bug fixes
v8.1.1
Bug fixes
Improve compliance with the official YAML test suite: #467, #469 and #475.
Make YamlMemberAttribute.DefaultValuesHandling actually usable. Fixes #466.
Actually inherit YamlIgnore attributes: #481.
New features
v8.1.0
New features and improvements
Previously, using an instance of
Serializer
orDeserializer
was not thread-safe,although the intention was for them to be thread safe. The only mutable state is
inside CachedTypeInspector and was not properly protected against concurrent mutation.
Other fixes
v8.0.0
New features and improvements
Change the default value handling behavior. Fixes #427
This is a breaking change to the default behaviour of the serializer, which will now always emit null and default values.
It is possible to configure this behaviour by using the
ConfigureDefaultValuesHandling
method onSerializerBuilder
.More details are available in the documentation.
Add default implementations for the following non-generic collections to
DefaultObjectFactory
:Remove obsolete and unused
SerializationOptions
enum. Fixes #438Throw descriptive exceptions when using the "linq" methods of
YamlNode
. Relates to #437Bug fixes
v7.0.0
Release 7.0.0
Added support for nullable references and netstandard 2.1.
Enabling nullable references exposed many potential bugs where the code assumed
that a reference would not be null, but where it was possible for it to be null.
In most cases this did not cause an error because of the way the code was being used.
Because fixing these problems required some breaking changes, a few improvements were made to the code base to take advantage of modern C# constructs.
Overall, the following breaking changes were made:
Removed the default constructor from most exceptions, because that would cause some uninitialized properties.
Made the
ParsingEvent
concretizations sealed. There is no point in inheriting from these because the library assumes that they form a closed set.Made many classes sealed, since they are not intended to be extended.
YamlDocument
now throws an exception if is has no root node after loading. This should only happen when loading from anIParser
that returns invalid data or is in an invalid state.The following APIs were made obsolete (but still work as before):
Refactored the extension methods to
IParser
to have better names with a more sensible semantic. The previous extension methods,Expect<T>
,Allow<T>
,Peek<T>
andAccept<T>
are still available but have been deprecated. The new extension methods are:T Consume<T>() where T : ParsingEvent
Ensures that the current event is of the specified type, returns it and moves to the next event. Throws an exception if the next event is not of the expected type.
bool TryConsume<T>(out T @​event) where T : ParsingEvent
If the event is of the specified type, returns it and moves to the next event, otherwise returns null.
T Require<T>() where T : ParsingEvent
Enforces that the current event is of the specified type.
bool Accept<T>(out T @​event) where T : ParsingEvent
Checks whether the current event is of the specified type.
Made the constructor of all naming conventions obsolete. Instead each has a static property named
Instance
. There was no point in creating multiple instances of those classes.Instead of:
Use:
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.