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

Plugin development environment should have proper field formats setup for index pattern #21273

Closed
aaronoah opened this issue Jul 26, 2018 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Plugins stale Used to mark issues that were closed for being stale Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc test

Comments

@aaronoah
Copy link
Contributor

Describe the feature:
Kibana plugin development under kibana-extra folder should have proper index pattern setup during tests.
Describe a specific use case for the feature:
e.g. the test_utils/stub_index_pattern file that is required by some of the tests file should pre-register some dumb field formats to prevent the browser tests from failing.

@timroes timroes added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc :Management triage_needed labels Jul 26, 2018
@epixa
Copy link
Contributor

epixa commented Aug 24, 2018

Can you clarify the issue you'd like to address with this? I'm not really following what the problem is.

@aaronoah
Copy link
Contributor Author

Sure. When a community vis plugin is being developed, we need to manually register dumb field formats for browser tests like this. Otherwise, the tests will fail because the default field formats in Kibana are not registered.

@epixa epixa added triage_needed bug Fixes for quality problems that affect the customer experience test Feature:Plugins and removed feedback_needed triage_needed labels Aug 27, 2018
@joshdover joshdover added the stale Used to mark issues that were closed for being stale label Jan 14, 2021
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 Feature:Plugins stale Used to mark issues that were closed for being stale Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc test
Projects
None yet
Development

No branches or pull requests

5 participants