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

[kbn-plugin-generator] Fix plugin naming inconsistency #20808

Merged
merged 3 commits into from
Jul 17, 2018

Conversation

aaronoah
Copy link
Contributor

Make relevant generated files use snakeCase instead of kebabCase
Closes #20524

@elasticmachine
Copy link
Contributor

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@timroes
Copy link
Contributor

timroes commented Jul 16, 2018

Jenkins, test this

Copy link
Member

@markov00 markov00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code LGTM.
The match between the .eslintrc rootPackageName and the plugin package.name is missing (the package name is in kebabCase). That is required by the eslint-import-resolver-kibana to property handle eslint on ES6 imports.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@markov00
Copy link
Member

12:13:09 Error: Proc "kibana" was stopped but never emitted either the "exit" or "error" event after 30000 ms

jenkins test this

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@markov00
Copy link
Member

jenkins test this

@markov00 markov00 added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v7.0.0 v6.4.0 refactoring labels Jul 17, 2018
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@markov00 markov00 changed the title Fix a bug of kbn-plugin-generator plugin naming inconsistency [kbn-plugin-generator] Fix plugin naming inconsistency Jul 17, 2018
@markov00 markov00 requested a review from spalger July 17, 2018 09:23
@@ -89,6 +89,7 @@ module.exports = function({ name }) {
kebabCase,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any reason to leave kebabCase here? Can we get rid of it and the lodash.kebabcase module?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, I've also checked this and it's no more used. @aaronoah could you check again and in case remove that line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@markov00 markov00 added the bug Fixes for quality problems that affect the customer experience label Jul 17, 2018
@markov00
Copy link
Member

Jenkins test this

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@spalger spalger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@spalger spalger merged commit 17eebb9 into elastic:master Jul 17, 2018
spalger pushed a commit to spalger/kibana that referenced this pull request Jul 17, 2018
<!--
Thank you for your interest in and contributing to Kibana! There
are a few simple things to check before submitting your pull request
that can help with the review process. You should delete these items
from your submission, but they are here to help bring them to your
attention.

- Have you signed the [contributor license agreement](https://www.elastic.co/contributor-agreement)?
- Have you followed the [contributor guidelines](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md)?
- If submitting code, have you included unit tests that cover the changes?
- If submitting code, have you tested and built your code locally prior to submission with `yarn test && yarn build`?
- If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed.
-->
Make relevant generated files use snakeCase instead of kebabCase
Closes elastic#20524
@aaronoah aaronoah deleted the plugin-gen-fix branch July 17, 2018 20:00
spalger pushed a commit that referenced this pull request Jul 18, 2018
…#20898)

Backports the following commits to 6.x:
 - [kbn-plugin-generator] Fix plugin naming inconsistency  (#20808)
@spalger
Copy link
Contributor

spalger commented Jul 18, 2018

6.4/6.x: 215c41c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience refactoring Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v6.4.0 v7.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants