Releases: goccy/go-yaml
Releases · goccy/go-yaml
1.9.4
1.9.3
New Features
- Support encoding and decoding
time.Duration
fields ( #246 ) - Allow reserved characters for key name in YAMLPath ( #251 )
- Support getting YAMLPath from ast.Node ( #252 )
- Support CommentToMap option ( #253 )
Fix bugs
- Fix encoding nested sequences with
yaml.IndentSequence
( #241 ) - Fix error reporting on inline structs in strict mode ( #244, #245 )
- Fix encoding of large floats ( #247 )
Improve workflow
1.9.2
1.9.1
1.9.0
New features
- Support encoding of comment node ( #233 )
- Support
yaml.NodeToValue(ast.Node, interface{}, ...DecodeOption) error
( #236 )- Can convert a AST node to a value directly
Fix decoder for comment
- Fix parsing of literal with comment ( #234 )
Rename API ( #235 )
- Rename
MarshalWithContext
toMarshalContext
- Rename
UnmarshalWithContext
toUnmarshalContext
1.8.10
Fixed bugs
- Fix searching anchor by alias name ( #212 )
- Fixing Issue 186, scanner should account for newline characters when processing multi-line text. Without this source annotations line/column number (for this and all subsequent tokens) is inconsistent with plain text editors. e.g. #186. This addresses the issue specifically for single and double quote text only. ( #210 )
- Add error for unterminated flow mapping node ( #213 )
- Handle missing required field validation ( #221 )
- Nicely format unexpected node type errors ( #229 )
- Support to encode map which has defined type key ( #231 )
New features
- Support sequence indentation by EncodeOption ( #232 )
1.8.9
Fix bugs
- Fix origin buffer for DocumentHeader and DocumentEnd and Directive
- Fix origin buffer for anchor value
- Fix syntax error about map value
- Fix parsing MergeKey ('<<') characters
- Fix encoding of float value
- Fix incorrect column annotation when single or double quotes are used
New feature
- Support to encode/decode of ast.Node directly