Fix output for aleph query --includeData
#189
Merged
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.
I noticed on Friday that the recent Statement class refactor in #177 broke the output of the
aleph query
command if you use it with the--includeData
flag. The "expanded" object body is included when you callinspect
, but not when you try to print theStatement
object as JSON.So this PR changes the way we override the depth of the
inspect
call. Instead of doing it in theStatement.inspect
method, we just return the JS object we want to print fromStatement.inspect
, and override the default inspect depth in the repl command. That way, in thealeph query
command, we can call.inspect()
on the query result and print it, including the embedded object.This is much cleaner anyway, since how you format the output shouldn't be tied to the Statement class. I think when I wrote the earlier impl I hadn't discovered that you can override
util.inspect.defaultOptions