Added support for unparseable sections.#72
Merged
Conversation
…latforms that handle whitespace differently.
Member
|
Thanks! |
unknwon
added a commit
that referenced
this pull request
Dec 21, 2016
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are public standards ( example: https://github.com/ADL-AICC/AICC-Document-Archive/releases/tag/cmi001v4 ) that are based around INI formats that allow for both standard key/value sections as well as sections that contain raw data that cannot be parsed. My attempt here is to provide a mechanism for leaving unparsed sections in their raw form, while otherwise meeting the INI parsing standards. It's off by default and can only be opted-into on a per-section basis by section name as part of the LoadOptions config. Tests included, and also cover the case-insensitive section names.