-
Notifications
You must be signed in to change notification settings - Fork 5
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
Generic Json API #3
Comments
I can provide more details if you need. |
The plugin expects an array with objects, it cannot process a deep tree. So, you have to transform the original schema. |
I just tested the plugin with above on-the-fly example. It does not work, because of a JSONata 1.8.5 bug: jsonata-js/jsonata#547 |
The old JSONata version is used by the datasource. It's a known issue and we have to wait for upgrading it: grafana/grafana-json-datasource#307 |
I see. So, the situation is more simple, because each field (Continent, Country, Company, Region, ...) has a dedicated level. The cause of "Fields have different lengths" error message is, a value is missing (because of not enough deep level) and must be substituted with a static string. The JsonPath is not enough flexible for it, so JSONata expression must be used, see (
You can use |
I have a tree represented in json that I would like to visualize in this component. I have managed to do so up until a certain level before I faced an issue. My tree is not "complete" meaning, one path has children that the other path does not. And a JSONPath selector such as
[?(@.items)]
does not solve the issue. Is this intended? My question is, if I define a "child level" for a certain "level" do "all nodes" at that level have to have that child?Imagine this:
As you can see, E does not have a level 3 child, but B does. Can this be represented with this component?
Here's my full json,:
The text was updated successfully, but these errors were encountered: