tonytins/cstdotnet
tonytins/cstdotnet
1
0
Fork 0
mirror of https://github.com/tonytins/cstdotnet.git synced 2026-02-10 12:14:47 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
cstdotnet/doc/changelog.md
Tony Bark 2789562abd Update CST class for nullability and debug interop 
- Changed preprocessor conditions to use DEBUG instead of NET8_0 for interop methods.
- Updated NormalizeEntries and GetEntry methods to accept nullable string parameters.
- Bumped project version to 2.1.101-alpha and updated changelog.
2026-01-07 04:25:06 -05:00

2 KiB
Raw Permalink Blame History

Change Log

2.1

2.1.101

  • Bumped target framework to .NET 10

2.1.100

  • Removed CaretSeparatedText in favor of CST class
  • Due to technical reasons, .NET Standard Standard support was removed

Experimental

  • Parser function can now be consumed from non-.NET programming languages.

2.0

2.0.104

  • Support for .NET 8

2.0.102

  • Properly commented and documented the rest of the code.

2.0.100

This version supports both .NET Standard 2.1 and .NET 6 and brings with it (much needed) quality of life changes internally. Apart from that, nothing has changed to the API itself apart from much needed documentation.

UIText class and interface

Based on FreeSO's API, the UIText class allows for traversing in /<directory>/<language>.dir directories and searching CST files by their Id number. (e.g. _154_miscstrings.cst). By defualt, the base path is /<program directory>/uitext/<language>.dir. You may also create your own implementation based on these APIs using the IUIText interface which mine also uses.

For more info, see usage.md.

1.0

1.0.300

  • Minor patch.

1.0.3

  • Backport switch to CSTNet namespace
  • Internal improvements.

1.0.2

  • Fixed the multiple line parsing in the v2 format.
  • Replaced "[ENTRY NOT FOUND]" message with "***MISSING***".

1.0.1

Despite only being a patch release, this includes a major refinement to the normalizing algorithm.

Rewrote normalizing algorithm

The normalizing algorithm has been rewritten to be more efficient and hopefully more reliable. The new algorithm de-constructs each line after converting it to the system's native line ending. Then it searches for the key and returns value. The rewrite also normalizes line endings to match the system's within the entry itself before returning the final output. This should make things more stable and predictable.

Known issues

  • Skipping comments is still a little buggy.
  • Multiline parsing with the v2 format is still a little unpredictable.

1.0.0

  • Initial release.