You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gilles (JIRA)" <ji...@apache.org> on 2017/08/15 23:41:00 UTC

[jira] [Commented] (CSV-215) CSVRecord mutability

    [ https://issues.apache.org/jira/browse/CSV-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128073#comment-16128073 ] 

Gilles commented on CSV-215:
----------------------------

Referring to code [here|https://github.com/apache/commons-csv/pull/21].

A {{CSVRecord}} "builder" class would be fine.
Forsaking the immutability of {{CSVRecord}}, much less so (cf. discussion on the ML).

> CSVRecord mutability
> --------------------
>
>                 Key: CSV-215
>                 URL: https://issues.apache.org/jira/browse/CSV-215
>             Project: Commons CSV
>          Issue Type: Improvement
>          Components: Parser
>            Reporter: Nitin Mahendru
>            Priority: Minor
>              Labels: features
>   Original Estimate: 16h
>  Remaining Estimate: 16h
>
> I recently pushed a change(pull request 20) to get the line ending from the parser.
> Now I want to push another change which I feel will also be useful for the community. I want to add a CSVRecordMutable class which had a constructor which accepts a CSVRecord object. So when we have a CSVRecordMutable object from it then we can edit individual columns using it.
> I would be using this to write back my edited CSV file. My use case is to read a csv, mangle some columns, write back a new csv.
> I could have directly raised a pull request but I just wanted to float the idea before and see the reaction.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)