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
If you have concrete suggestion for additional functionality (or even a general idea), yes, feel free to add here.
At this point polymorphic handling is not really supported.
If this is more of a question (or start of discussion), please use mailing list:
I've hit this issue recently in work. I used your CsvSchema classes to speculatively detect polymorphic array members already... Then found that the csv itself wouldn't deserialize because the JsonParser attached to the CsvMapper has only a single CsvSchema attached. I can apply the same concepts I used for the validation here to inspect the JsonTypeInfo data and swap out the CsvSchema on the JsonParser based on the type field. It's a bit of an overhaul as there's a few ways to apply the polymorphic typing with Jackson but I'm going to have a crack at this and try get a PR in for you. Also, I may separately extend the column types to allow validating types a bit more accurate, ie. Distinguish between decimals and integers and potentially do a bit of date detection. Polymorphism first though. Are you guys open to PRs? I should be able to keep the performance impact as close to negligible as possible. It could be zero'd out if I make polymorphic handling a DeserializationFeature that has to be turned on by default.
Can the CSV mapper handle polymorphic reading and writing. If it can could you show a quick example?
The text was updated successfully, but these errors were encountered: