Releases: dlang-community/D-YAML
v0.10.0: Support for ':' and '?' in flow context, fix recent deprecation, various internal improvements
What's Changed
- Fix #309: Not to include
\0
in the resulted token byscanBlockScalar
by @tom-tan in #310 - fix missing filename in token tests by @Herringway in #313
- add an example app for dumping the tokens of a yaml document by @Herringway in #312
- remove SliceBuilder and Transaction by @Herringway in #315
- don't skip explicit str tags when emitting by @Herringway in #317
- make sure assertEventsEqual() actually has events to test by @Herringway in #316
- remove Loader.parse() by @Herringway in #319
- move Loader.scanBench into benchmark tool by @Herringway in #318
- simplify loader initialization by @Herringway in #320
- replace Mark-esque bits of Scanner.SimpleKey with an actual Mark instead by @Herringway in #321
- implement string representation for tokens by @Herringway in #322
- add more detail to test suite runner by @Herringway in #323
- correct an assert() in Scanner.fetchValue, have it occur earlier by @Herringway in #326
- fix #325 - null simple keys not properly nullified by @Herringway in #327
- support : and ? in flow context as per updated YAML spec by @Herringway in #328
- revamp exception handling by @Herringway in #329
- Fix a DMD 2.109.0 deprecation by @Herringway in #332
Full Changelog: v0.9.2...v0.10.0
v0.9.2: Relax anchor/aliases restrictions, improve API and error messages
What's Changed
- do proper character substitution in yaml test suite by @Herringway in #305
- relax restrictions on anchors/aliases to closer match current YAML spec by @Herringway in #299
- Improve and correct error message on duplicated keys by @Geod24 in #306
- Allow to pass an explicit filename to Loader.fromString by @Geod24 in #307
- CI: Update actions version by @Geod24 in #308
Full Changelog: v0.9.1...v0.9.2
v0.9.1: Support forward slashes in strings
This release introduce support for optionally-escaped forward slashes in string, which improve JSON compatibility.
This is especially important in the D ecosystem, as Vibe.d escapes forward slashes by default.
What's Changed
- fix flow style sequences and collections events in test suite by @Herringway in #298
- add .pdb files to gitignore by @Herringway in #304
- Fix #302: Support escaped forward slashes by @Geod24 in #303
Full Changelog: v0.9.0...v0.9.1
v0.9.0: Compatibility with DIP1000
D-YAML can now be compiled with -preview=dip1000
. In order to do so, usage of Variant
was replaced by std.sumtype
.
This should reduce reliance on TypeInfo
and memory usage.
What's Changed
- Add missing annotations to exceptions ctor by @Geod24 in #293
- Node: Replace usage of Variant with SumType by @Geod24 in #291
- constructor: Use new RedblackTree instead of redBlackTree function by @Geod24 in #292
- Add attributes to type / nodeID / nodeTypeString by @Geod24 in #294
- Refactor some
Node.opCmp
code by @Geod24 in #295 - Fix #184: Support for DIP1000 by @Geod24 in #296
Full Changelog: v0.8.6...v0.9.0
v0.8.6: Clean and Compatible
v0.8.5: New logo and easier error mark access
v0.8.4: Exposing YAML node source informations, better support for `const`
User-visible changes since v0.8.3:
- Added the ability to get the start position (file, line, column) of a
Node
(#263 + #264);
This allows users to expose rich informations when an error triggers during YAML parsing. - Improve CTFEability (#266);
- Improved support for type constructors (
const
,inout
...) for constructors (#268); - Made
Node.get
inout
, allowing it to work onconst Node
(#269); - Fixed Meson build version (#274);
Minor bugfixes
v0.8.2: Remove wrongly applied 'in' on parameters
This removes 'in' qualifiers on delegate parameters to parseFlowKey
and parseFlowValue
. This should have no effect on user code,
but will to use -preview=in
(which set in
to mean scope const
)
with D-YAML.
v0.8.1
Fix some deprecations and other bugs