Skip to content

Conversation

@wryun
Copy link

@wryun wryun commented Aug 9, 2017

See #11

@danvk
Copy link

danvk commented Feb 18, 2018

+1, this would allow jp to work with ndjson. I'd even argue that this should be the default behavior of jp, rather than hidden behind a flag. This is how jq works.

@lostinthefrost
Copy link

+1, and I agree this should be the default behavior.

@suntong
Copy link

suntong commented Jun 5, 2021

Now available in https://github.com/go-jsonfile/jp/releases/tag/v0.1.5

@wryun
Copy link
Author

wryun commented Jun 5, 2021

Heh, well, if we're saying that, it's been available at https://github.com/wryun/jp for a few years now (with other useful additions) :)

EDIT: not to say it wouldn't be a good thing if someone picked up jp and started maintaining it, which I'm definitely not going to do. Good luck!

zmedico pushed a commit to pipebus/jpp that referenced this pull request Jun 15, 2021
zmedico added a commit to pipebus/jpp that referenced this pull request Jun 15, 2021
@zmedico
Copy link
Contributor

zmedico commented Jun 15, 2021

+1, this would allow jp to work with ndjson. I'd even argue that this should be the default behavior of jp, rather than hidden behind a flag. This is how jq works.

+1, and I agree this should be the default behavior.

Now available in https://github.com/go-jsonfile/jp/releases/tag/v0.1.5

Also available as the default behavior in jpp, an extended superset of the jp command: #30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants