-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[NP] Change plugin ids to camel case #56620
Conversation
# Conflicts: # src/legacy/core_plugins/kibana/public/home/plugin.ts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started to comment in all places, but there are too many - please only change the NP plugin id, not the feature id, role names or the route - these changes could cause backwards compatibility problems for existing clusters.
This is just about the id
in the kibana.json and the property in the plugins
object in setup and start contracts of consuming plugins
@elasticmachine merge upstream |
merge conflict between base and head |
# Conflicts: # src/legacy/ui/public/new_platform/__mocks__/helpers.ts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, didn't test locally
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (reviewd, but didn't test locally as well)
# Conflicts: # src/legacy/core_plugins/kibana/public/dashboard/plugin.ts
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-app (Team:KibanaApp) |
Fixes #55363
This PR includes renaming NP plugin ids to use camel case:
devTools
instead ofdev_tools
;kibanaLegacy
instead ofkibana_legacy
.