-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Depricated Plugin #415
Comments
Hi @giorgiimnadze11 there's already a fork with a newer version of flowcharting, send you a link below. It solves the problem with Angular, it still undergoing testing. |
Ah so much for optimism. No, no, no, the fork does not fix the Angular problem. |
maybe someone can do a request to migrate from angular to react if he knows on the new fork |
The new fork was for our usage. |
Oh, I thought so... 😢 |
I think that we should petition GrafanaLabs to take a look at this. This plugin is very useful and GrafanaLabs has nothing that comes close to functionality offered by it. Maybe it is an option for them to adopt the project ? |
created a petition https://chng.it/FVjYwTP27D please sign in |
created a page in grafana community https://community.grafana.com/t/urge-grafanalabs-to-migrate-flowcharting-plugin-from-angular-to-react-to-keep-the-plugin-alive/110548 |
Grafana has nothing to do with FlowCharting v0.9.1 plugin! FlowCharting v0.9.1 is opensource community plugin for Grafana! |
Hello,
I use Grafana Enterprise v9.5.1 (bc353e4b2d) and Plugin FlowCharting v0.9.1.
When I add FlowCharting plugin wrote me a message that if Angular is not replaced in the new version, then this plugin will be disabled from the tenth version of Grafana.
I contacted the Grafana support team and they also told me that if the developers of this plugin do not replace Angular, then the plugin will be disabled.
Please let me know if you plan to update this plugin and support it in the future.
I'm using this plugin with draw.io to draw server racks and I'm wondering if it will stop my dashboard from working.
The text was updated successfully, but these errors were encountered: