VDFparse v4.2

Full Changelog: v4.0...v4.2

v4.0

The base structure has been reworked once again by removing the intermediate format and outputting directly as json. While this makes interop with the format impossible, it increases parsing throughput by ~10x. Also unused dataset items will be skipped instead of fully parsed if possible.

This comes with the downside that duplicate keys might be in the output. If any problems arise of this, do open an issue.

v3.1

What's Changed

• Add support for the new (2022-12) appinfo format by @Spodi
• Fix bug when no id was passed as an argument

v3.0: New direction

This release completely removes the querying functionality of the program and only converts the output to json.
This is a deliberate choice, as filtering and parsing can more easily and efficiently be done by a tool like jq.

If filtering over the same set multiple times, consider writing the output to an intermediate json.

For VDFparse.Core the main change is that we expose static VDFFile.Read() as a means to implicitly parse a file.
If manual parsing is required, consider extending VDFFile.Readers or manualy calling the parser functions of IVDFFileReader or KVParser.

For VDFparse.Cli we use CommandLineParser to generate a simpler to use cli interface. use vdfparse --help to get more info.

Add support for both UTF8 and UTF16

Fix support for both UTF8 and UTF16

Dont cast to char and append directly, but instead use `Encoding` class to convert the data in the buffer.
Also set Console output to UTF8 mode for cases where it outputs UTF8 but isnt set yet

Allow '*' as wildcard for appid

v2.2.0

Add support for '*' as a wildcard on first entry

v2.1.2: Fix Display Error

Fix displaying of Values

v2.1.0

Initial upload