-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change the result column headers #249
Comments
That would be nicer output, but it would be much harder and slower to do.
During conversion, it would have to sort of "look down" into each element
and check to see if any keys match and perform special logic, which is
expensive. The current approach is there because it can just walk through
every level of the object without caring about "nephews/nieces" it as it
assembles each column header. So, it's unlikely to change.
…On Sun, Sep 20, 2020, 8:09 AM vstepaniuk ***@***.***> wrote:
Would be nice to change the result column headings for
[{"a":[{"b":0},{"b":1}]}]
from
*a/0/b*, *a/1/b*
to
*a/b0*, *a/b1*
or
*a/b1*, *a/b2*.
What do you think?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#249>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAABD4BT6OQ3P6S6NSUCLJDSGYLI3ANCNFSM4RTV3SHQ>
.
|
You could just post-process the column headings after the conversion is finnished |
and I don't see how it makes it more difficult to process - we just need to change the headings |
vstepaniuk
changed the title
Change the result column headings
Change the result column headers
Oct 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would be nice to optionally change the result column headers for
[{"a":[{"b":"c"},{"b":"d"}]}]
from
a/0/b, a/1/b
to
a/b0, a/b1
or
a/b1, a/b2.
What do you think?
The text was updated successfully, but these errors were encountered: