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
{{ message }}
This repository has been archived by the owner on Oct 16, 2023. It is now read-only.
Currently, only entity fields of type String will be parsed when using a parsing object with annotations. Should be possible to cover default types and add custom type converters based on column name, or specified in the annotation.
Global .withTypeConverter function should remain, but declaring converters on annotation level makes sense if there are different formattings of the same date type in one file for example.
Evaluation if .withTypeConverter makes sense for parsing as well, which should as we can match against the type of the field related to the column name.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, only entity fields of type String will be parsed when using a parsing object with annotations. Should be possible to cover default types and add custom type converters based on column name, or specified in the annotation.
Global .withTypeConverter function should remain, but declaring converters on annotation level makes sense if there are different formattings of the same date type in one file for example.
Evaluation if .withTypeConverter makes sense for parsing as well, which should as we can match against the type of the field related to the column name.
The text was updated successfully, but these errors were encountered: