[
https://issues.apache.org/jira/browse/CSV-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018482#comment-15018482
]
Gary Gregory commented on CSV-163:
----------------------------------
I do not understand the example, it looks like a mix of two examples, one for
mapped access, one for indexed access.
Regardless, I think this is out of scope. [CSV] is just about parsing and
emitting. Mapping objects enters the territory that is well worn by other
frameworks like JPA, granted JPA is heavy in comparison, but I do not to invest
yet another mapping DSL...
> add a basic mapping feature
> ---------------------------
>
> Key: CSV-163
> URL: https://issues.apache.org/jira/browse/CSV-163
> Project: Commons CSV
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
>
> would be neat to be able to map records instead of using string based access:
> {code}
> public class MyRecored {
> @Csv(position = 1) String name;
> @Csv(name = "city") String city;
> // ...
> }
> {code}
> Think it is acceptable to support only basic types (primitives + String/Date
> to start). This constraint would keep the code light and simple - no
> converter - but easier to use than "map"-like API .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
