Np kibana plugin home feature catalogue#50838
Conversation
…ver_tutorials_api
…orm tutorial plugin registrations
… tutorials service
… the home plugin public folder
💚 Build Succeeded |
…gin_home_feature_catalogue
|
💔 Build Failed |
|
@elasticmachine merge upstream |
💚 Build Succeeded
|
flash1293
left a comment
There was a problem hiding this comment.
Code changes LGTM, didn't pull down to test
…gin_home_feature_catalogue
f4548b2 to
a485ba2
Compare
…gin_home_feature_catalogue
|
@joshdover I need a |
💚 Build Succeeded |
joshdover
left a comment
There was a problem hiding this comment.
Looks great! Just two small suggestions.
I think it might be clearer if the services directory had top-level directories for each service so the source files don't get mixed up. For example:
services/
feature_catalogue/
index.ts
feature_catalogue_registry.ts
other_service/
index.ts
other_services.ts
index.ts
May want to change the server-side as well.
Co-Authored-By: Josh Dover <me@joshdover.com>
I was thinking the same thing! I'll do that in this PR because the next task is to migrate the |
💚 Build Succeeded |
💚 Build Succeeded |
* Moves feature_catalogue services into the home plugin public folder.
Summary
Moves the feature_catalogue plugin (introduced in PR48818 ) into the home plugin.
Dev Docs
The
ui/registries/feature_cataloguemodule has been deprecated for removal in 8.0Plugins wishing to migrate may remove their usage of
ui/registries/feature_catalogueand rely on either:Note that the old module supported providing a Angular DI function to receive Angular dependencies. This is no longer supported as we migrate away from Angular.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.- [ ] This was checked for cross-browser compatibility, including a check against IE11- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers