-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulty treating some numeric tags as string #646
Comments
We're glad you find this project helpful. We'll try to address this issue ASAP. You can vist https://solothought.com to know recent features. Don't forget to star this repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have an input structure where some numeric values are to be treated as strings. Rather than calling
toString
in multiple places in my code, I hoped to use the parsing options, but looking at the codebase I think it is not currently possible using either numberOptions or tagValueProcessor.Input
Code
Output
expected data
I see why there is no conversion - the input type is string and so is the output type, so when the tagValueProcessor is applied, parsing is not skipped.
I can't use the
skipLike
property ofnumberParseOptions
becausestrnum
only receives the value without the tag name for context. I can't safely use a regex to differentiate IDs from other numbers.I can't use the
parseTagValue
option because that is a universal setting that can't be applied to specific tags.I think the simplest (backward compatible) approach that would work for me, would be another option like parseTagValue, but which takes a function with the same inputs as tagValueProcessor or isArray, and returns boolean, so that enabling parsing can be finer grained.
Would you like to work on this issue?
Bookmark this repository for further updates. Visit SoloThought to know about recent features.
The text was updated successfully, but these errors were encountered: