Skip to content
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

[FeatureRequest] Plugins: Allow panel plugins to update queries from the visualization component #18573

Closed
mousavihasans opened this issue Aug 15, 2019 · 2 comments

Comments

@mousavihasans
Copy link

Dear all,

I have asked my question in the Grafana Community but unfortunately nobody has answered it. The question is very important and lake of documentation for developing a Grafana plugin is really unacceptable.

I am going to develop a Grafana plugin (using ReactJS and Typescript) in which I need to update the query that the plugin receive. Right now, I can get the query and represent its item but I am not able to update the query based on user input in the plugin panel. I have search for the answer but I cannot find it. I have just found two clues. According to this video I should use QueryEditorProps (the speaker mentioned it in the question and answer section without any coding). Also, I might use template variables in the query and update these variables to update query.

@torkelo
Copy link
Member

torkelo commented Aug 15, 2019

This is currently not possible. Queries can only be updated from the query editor.

@torkelo torkelo changed the title Update a panel plugin query within the plugin (ReactJS and Typescript) Plugins: Allow panel plugins to update queries from the visualization component Aug 15, 2019
@hugohaggmark hugohaggmark changed the title Plugins: Allow panel plugins to update queries from the visualization component [FeatureRequest] Plugins: Allow panel plugins to update queries from the visualization component Nov 11, 2020
@grafanabot
Copy link
Contributor

This feature request has been open for a long time with few received upvotes or comments, so we are closing it. We're trying to limit open GitHub issues in order to better track planned work and features.

This doesn't mean that we'll never ever implement it or that we will never accept a PR for it. A closed issue can still attract upvotes and act as a ticket to track feature demand/interest.

Thank You to you for taking the time to create this issue!

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

No branches or pull requests

4 participants