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

[DOCS] Update "Migrating from legacy plugins examples" to match our STYLEGUIDE #91124

Closed
afharo opened this issue Feb 11, 2021 · 3 comments
Closed
Labels
DevDocs docs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented Feb 11, 2021

We've noticed that our migration example demoplugin does not match our STYLEGUIDE.

Let's take some time to revisit the examples and add a link to the style guide.

@afharo afharo added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc docs DevDocs labels Feb 11, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@joshdover
Copy link
Contributor

Scope to only updating naming conventions that produce warnings (kibana.json, etc.)

@pgayvallet
Copy link
Contributor

"Legacy" plugins starts to become a very old concept. I think we're safe to close this.

@pgayvallet pgayvallet closed this as not planned Won't fix, can't repro, duplicate, stale Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevDocs docs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants