You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from Grafana 10, plugins can start using the v6 of react-router. Overall, react-router v6 aims to simplify route configuration and provide a more flexible and intuitive API for developers.
Why?
We are going to deprecate using react-router v5 in plugins from Grafana 11, and we would like to make sure our internal app plugins are using the v6 version by the time we finish migrating Grafana core itself.
How?
We have created a migration guide for plugins (please see the links below), and also don't hesitate to reach out in #grafana-plugins-platform in Slack in case you have any questions.
added this to "To Be Groomed" because it appears we are currently using a deprecated version of react router (Grafana 11 has been out for ~2 months as of the writing of this comment)
Opened a PR #4703 for it - it changes OnCall so that we rely on the react-router-compat version but its using v6 syntax. Can't fully migrate to v6 as grafana/scenes still relies on v5 and that seems to break rendering on the Insights page
Starting from Grafana 10, plugins can start using the v6 of react-router. Overall, react-router v6 aims to simplify route configuration and provide a more flexible and intuitive API for developers.
Why?
We are going to deprecate using react-router v5 in plugins from Grafana 11, and we would like to make sure our internal app plugins are using the v6 version by the time we finish migrating Grafana core itself.
How?
We have created a migration guide for plugins (please see the links below), and also don't hesitate to reach out in
#grafana-plugins-platform
in Slack in case you have any questions.The text was updated successfully, but these errors were encountered: