Resolves #48 Make the PropertyFetcher case insensitive #49
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
austinlparker
approved these changes
Aug 21, 2019
|
CI takes care of versioning when we make a release tag. Thanks for the fix! |
|
Any timeline on getting a release that contains this fix? |
|
Looks like release 0.6.1 was just created with this change in it! |
|
It was! Happy Thursday. :) |
|
Woo hoo! Thanks! |
|
Thanks again for creating the release. At what point will that get pushed to nuget? |
|
I published it a few minutes ago, so it should show up within the hour. Thanks for your patience! |
|
Awesome, thanks again! |
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.
Details about the issue in #48
Do I need to do anything else for the release (for example bumping the version, etc.), or everything else is taken care of by the CI build?