Let you choose the Culture used for TypeConversion in the processor #79
Conversation
This file contains 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
|
Any update on this @Biarity :) ? |
yannickdp
pushed a commit
to yannickdp/Sieve
that referenced
this pull request
Apr 27, 2021
…ersion in the processor Biarity#79
|
This is addressed in #125 . @yannickdp please review that PR. |
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.
Hello,
It would be nice to be able to choose the culture used for type conversion in the processor.
I have an API which have french as the default culture and this feature would let me force "english" as the culture used in the processor : I would be able to use decimal not formatted in french (comma can't be used because the SieveModel already uses them to separate filters) but in english in the processor.