-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
add new --run-examples flag #52031
add new --run-examples flag #52031
Conversation
Pinging @elastic/kibana-platform (Team:Platform) |
Pinging @elastic/kibana-operations (Team:Operations) |
@@ -237,7 +247,7 @@ export default function (program) { | |||
silent: !!opts.silent, | |||
watch: !!opts.watch, | |||
repl: !!opts.repl, | |||
basePath: !!opts.basePath, | |||
basePath: opts.runExamples ? false : !!opts.basePath, |
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.
The reason to use no base path here is that we can use links into our examples in our api documentation, much like we have the View in Console
links, that links to http://localhost:5601/kibana/demoSearch/...
. We can link to these samples with a note that says, "be sure to running a local kibana with the --run-examples
flag"
💚 Build Succeeded |
I was able to make faster progress on the bigger PR so this can be closed in favor of #52027 |
Closing in favor of #52027 |
To test yarn
yarn start --run-examples
and see that the search explorer is available.Ideally I would switch the functional test running to use this flag, but I need to separate out the example plugins and the plugins that exist only for testing purposes. I started that effort here https://github.com/elastic/kibana/pull/52027/files but ran into issues with adding a new top level
examples
folder with these plugins.So, that is the end goal, to have a top level examples folder that houses these plugins that are supposed to be more public (#26781) but that will involve a bit more effort, and so I can at least just make it easier to run these things, I pulled this little piece out.
Next steps, in parallel with that above effort, will be to add a new Embeddables example folder that is meant more for public consumption, is a new platform plugin, and add that. Then I would like to write a blog post, and be able to reference the command (
yarn start --run-examples
) instead of showing the much longer--plugin-path
version.