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
As part of our ongoing efforts to improve the OpenSearch Dashboards' performance, maintainability, and developer experience, we have decided to de-angularize the dashboard.
This change will impact all plugins that use the OpenSearch Dashboard dashboard and require your attention to ensure the compatibility and performance of your plugins. If your plugin has nothing to do with dashboard, please close the issue.
We suggest a thoroughly test of your plugin on new dashboard. Here are some steps:
Run all the tests. Also recommend to do manual tests.
We understand that this transition may require significant work on your part, and we are here to support you during this process. If there is any concerns or issues, feel free to comment here. If there is a bug, please also add it to #4505.
The text was updated successfully, but these errors were encountered:
Description
As part of our ongoing efforts to improve the OpenSearch Dashboards' performance, maintainability, and developer experience, we have decided to de-angularize the dashboard.
This change will impact all plugins that use the OpenSearch Dashboard dashboard and require your attention to ensure the compatibility and performance of your plugins. If your plugin has nothing to do with dashboard, please close the issue.
We suggest a thoroughly test of your plugin on new dashboard. Here are some steps:
Pull this feature branch https://github.com/opensearch-project/OpenSearch-Dashboards/tree/feature/deangular-dashboards.
Install and start your plugin.
Run all the tests. Also recommend to do manual tests.
We understand that this transition may require significant work on your part, and we are here to support you during this process. If there is any concerns or issues, feel free to comment here. If there is a bug, please also add it to #4505.
The text was updated successfully, but these errors were encountered: