You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm reaching out regarding the keepStrings flag. Currently, this flag controls the type conversion for both numbers and booleans uniformly. In my use case, I require more flexibility to sometimes convert numbers but keep booleans as strings, or vice versa, depending on the particular data representation I need when converting XML to JSON.
So, I am wondering about your thoughts to allow separate control over the type conversion for numbers and booleans.
I believe this change would align with the project's goals to address a major user inconvenience and could be achieved without breaking existing behavior (I'm still reviewing the source code, and would appreciate your comments on feasibility of such a change). Allowing users more control over the data representation would be highly beneficial. Thanks.
The text was updated successfully, but these errors were encountered:
@jagsgill Sounds reasonable, no objections to adding more granular flags for this purpose. Please use XMLParserConfiguration, avoid changing any constructors for this class, and use with*() methods to set the new values (there are plenty of example methods in that file). Try to use common and easily understood names for the new flags. Also, please add appropriate comments to the keepStrings flag and the new flags. Don't forget to add unit tests. Thanks!
Hello JSON-java maintainers,
I'm reaching out regarding the
keepStrings
flag. Currently, this flag controls the type conversion for both numbers and booleans uniformly. In my use case, I require more flexibility to sometimes convert numbers but keep booleans as strings, or vice versa, depending on the particular data representation I need when converting XML to JSON.So, I am wondering about your thoughts to allow separate control over the type conversion for numbers and booleans.
I believe this change would align with the project's goals to address a major user inconvenience and could be achieved without breaking existing behavior (I'm still reviewing the source code, and would appreciate your comments on feasibility of such a change). Allowing users more control over the data representation would be highly beneficial. Thanks.
The text was updated successfully, but these errors were encountered: