On Sun, Jun 14, 2020 at 12:43 PM Tatu Saloranta <
ta...@fasterxml.com> wrote:
>
> On Sun, Jun 14, 2020 at 12:01 PM Marek Andreánsky <
ma...@andreansky.sk> wrote:
> >
> > Thanks for the reply, that is what I thought as well - getting it out as a string and parsing it, but was researching if it can be done in a more elegant way via the library. I could open an issue or enhancement request on GitHub for this if you think its worthwhile to keep track of.
> >
> > Would be nice if we could specify enclosing tags for an array inside csvs without resorting to parsing strings as I did encounter similar notations (array elements in square brackets separated by colons) before.
> >
> > And the tools I used to inspect the csv (Rons csv editor and VS code) all said the csv is valid.
>
> If decoding of CSV content fails, when attempting to bind to a String
> property, that is probably worth filing an issue for,
> as that is bit different question? I can't say for sure without
> looking deeper but that could be a bug.
... also, forgot to ask one more thing: if you are aware of any
specification or guidance for "bracket arrays in CSV" notation, a link
would be nice to support need. There are many de-facto conventions as
there isn't really definitive CSV specification even just for basic
things, but many conventions supported by various tools. I would be
happy to add links from CSV module repo to various document usages,
even if just to point that specific one is not explicitly supported.
It would also be easier to figure out how likely some
features/notations are to be used by large number of people: sometimes
feature requests are just for usage within one company, for example,
and other times larger ecosystems use specific variation.
Knowing context helps evaluate things.
-+ Tatu +-