Releases: dduan/TOMLDecoder
Releases · dduan/TOMLDecoder
0.3.3
- Align Apple platforms to iOS 12 / macOS 10.14 / tvOS 12 / watchOS 5
- Fix compile error on iOS for the compliance executable target
0c2ac3564a20cd0a9a9ebf52e7c73529e7a6416271a459070506034d309a8655 0.3.3.tar.gz
f74bfc65515ae648c2e047dc06dda80fdb69d099e791b08eb6bb0bcf437720b8 0.3.3.zip
0.3.2
0.3.1
0.3.0
- Lowercase "z" is now accepted as zero-timezone-offset indicator
- Space is no longer accepted as an escaped character
- Hex/Octal/Binary numbers with no digits surrounding
_is considered invalid - Comments or whitespace at start of document no longer causes parsing failure
- TOML with invalid UTF-8 byte sequence will be rejected. Previously these have
been decoded with the replacement character (U-FFFD). - Local date with a trailing
Tsuch as2023-04-16Tis considered invalid. - Day with value
00is invalid. - Allow defining super table after it has been implicitly defined. For example,
one could define[a.b.c], then later[a]. - Using dotted keys to add up to a previously header-defined table is now
invalid. For example, use[a.b.c]to create the table, and later have
b.c =under[a]. - A standalone carriage return is no longer considered a valid newline
- Inline tables are now immutable
- Mutating array of tables that were implicitly created (e.g.
a = [{}]) is now
invalid - Keys with spaces in between segments are now valid
- Multiline strings can now have 1 or two quotes as valid content
- Local date with a comment (
1970-01-01 # some comment) is now accepted - Control characters (except taps) in comments are now invalid
- Escaped CLRF character in multiline string is properly handled
0.2.2
0.2.1
- Include a new type
DeserializationError. It contains information regarding
deserialization. - Improve error reporting. After encountering one error, the parser will
disgard characters until new line, and attempt to parse another top-level
expression. This is more determinastic compared to previous recovery attempts. - Add more specific errors regarding missing pices at closing position. For
example, string missing closing quotes, or table missing closing bracket.
These errors will cause the parser to report detailed error message. - Fix a bug where newline characters sometimes are considered valid as part of
basic string content.
0.2.0
- Rewritten from scratch to support TOML Spec 1.0
- Remove support for CocoaPods and Carthage
- Remove dependency on NetTime, parser returns
Foundation.Dateand
Foundation.DateComponentsinstead. - Remove SwiftPM dependency on the
TOMLDeserializerpackege. It has been
merged into the same project. - Improved error reporting: a parsing error won't cause parsing to stop.
Instead, the parser will attempt to parse as much as possible and report all
errors it encounters.
0.1.6
Bump version to 0.1.6
0.1.5
Bumb release to 0.1.5