Hello,
I’m an independent developer currently implementing a blockchain library.
One of my goals is to create a CLI tool that can inspect the blockchain’s on-chain database content.
For example, the command might look like this:
planet repo inspect .data/db --query <expression>
While exploring ways to achieve this, I discovered JMESPath and found this project through GitHub.
Although I haven’t directly used it yet, I reviewed the code and discussed it with GitHub Copilot.
However, I wasn’t able to find a way to accomplish what I need.
As far as I understand, to use query expressions, we need to pass JSON data to the JmesPath.Transform method.
But in my case, the underlying data comes from a database that could become very large, making full JSON serialization impractical.
It would be extremely useful if there were an interface or mechanism to query non-JSON data directly, for example through a stream or a custom adapter, rather than needing to serialize everything into JSON first.
Is there any plan or consideration to support this kind of functionality in the future?
Thank you!
Hello,
I’m an independent developer currently implementing a blockchain library.
One of my goals is to create a CLI tool that can inspect the blockchain’s on-chain database content.
For example, the command might look like this:
While exploring ways to achieve this, I discovered JMESPath and found this project through GitHub.
Although I haven’t directly used it yet, I reviewed the code and discussed it with GitHub Copilot.
However, I wasn’t able to find a way to accomplish what I need.
As far as I understand, to use query expressions, we need to pass JSON data to the JmesPath.Transform method.
But in my case, the underlying data comes from a database that could become very large, making full JSON serialization impractical.
It would be extremely useful if there were an interface or mechanism to query non-JSON data directly, for example through a stream or a custom adapter, rather than needing to serialize everything into JSON first.
Is there any plan or consideration to support this kind of functionality in the future?
Thank you!