XML config parity with JSON #167
Merged
Conversation
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
|
The updated External Configuration section of the revised docs covers all the options: |
|
I'm satisfied with the results of my testing, so I'll leave this open for feedback for a few days before merging. (Unless another reviewer feels it's good to go and merges, of course!) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Significantly expands XML configuration support. Now, just like configuration in .NET Standard, all options can be configured except the
Propertiesfilter predicate (for the same reasons -- it would require Roslyn compiler overhead that isn't warranted).fixes #80
fixes #119
I'll be doing a little more testing before I merge but I wanted to get the PR in the pipeline now.