Automatically decode from pathnames/streams in jget.
#16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This way, it's easier for quick-and-dirty json indexing on files and streams, without the need to parse them first. String-parsing is not supported due to it being ambiguous: - Is it a string to be parsed and then acted upon? - Or is it a string that is erroneously indexed with wrong indices? Closes atlas-engineer#15.
|
Btw, maybe transfer the repo ownership to me to ease the maintenance burden and allow me to evolve my brainchild? |
|
@aadcg, any review? |
|
@aartaka not a priority at the moment, thanks. |
|
aartaka not a priority at the moment, thanks.
No problem, I'm not in a hurry.
But that's partly why I'm suggesting ownership transfer. I'm ready to maintain this library and iterate on it. I have lots of ideas for improvement too!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This way, it's easier for quick-and-dirty JSON indexing on files and streams, without the need to parse them first.
String-parsing is not supported due to it being ambiguous:
Closes #15.