mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
# Backport This will backport the following commits from `main` to `8.x`: - [[Dashboard] Remove mSearch from content management (#210709)](https://github.com/elastic/kibana/pull/210709) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nick Peihl","email":"nick.peihl@elastic.co"},"sourceCommit":{"committedDate":"2025-03-03T16:31:09Z","message":"[Dashboard] Remove mSearch from content management (#210709)\n\n## Summary\n\nRemoves the mSearch method from Dashboard content management.\n\nThe `mSearch` content management method was designed to be a temporary\nimplementation of search that allowed searching multiple saved object\ntypes ([see more\n[internal]](https://docs.google.com/document/d/1ssYmqSEUPrsuCR4iz8DohkEWekoYrm2yL4QR_fVxXLg/edit?tab=t.0#heading=h.6sj4n6bjcgp5)).\nHowever, the mSearch implementation in the Dashboard Storage class lacks\nextensibility as it requires a synchronous `toItemResult` function. As\nwe start migrating reference handling to the server, we will likely need\ntransforms that return Promises (ex. `savedObjectToItem`), such as\n[retrieving tag saved objects from the SavedObjectTagging\nclient](https://github.com/elastic/kibana/issues/210619).\n\nThe Dashboard `mSearch` method was only used by the dashboard_picker and\nthis PR replaces its usage with the `search` method.\n\n### Identify risks\n\nThere is a slight risk in serverless environments where a browser may\nhave already loaded the dashboard_picker module but lags behind the\nserver. In this case, the dashboard picker may fail to retrieve a list\nof dashboards due to it calling the now non-existent `mSearch` method\nprovided by the server. In this case, the user simply needs to refresh\ntheir browser to retrieve the latest UI modules.","sha":"2a7e38b0fc3c33921f5a29f427bc3a6de8809c67","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"[Dashboard] Remove mSearch from content management","number":210709,"url":"https://github.com/elastic/kibana/pull/210709","mergeCommit":{"message":"[Dashboard] Remove mSearch from content management (#210709)\n\n## Summary\n\nRemoves the mSearch method from Dashboard content management.\n\nThe `mSearch` content management method was designed to be a temporary\nimplementation of search that allowed searching multiple saved object\ntypes ([see more\n[internal]](https://docs.google.com/document/d/1ssYmqSEUPrsuCR4iz8DohkEWekoYrm2yL4QR_fVxXLg/edit?tab=t.0#heading=h.6sj4n6bjcgp5)).\nHowever, the mSearch implementation in the Dashboard Storage class lacks\nextensibility as it requires a synchronous `toItemResult` function. As\nwe start migrating reference handling to the server, we will likely need\ntransforms that return Promises (ex. `savedObjectToItem`), such as\n[retrieving tag saved objects from the SavedObjectTagging\nclient](https://github.com/elastic/kibana/issues/210619).\n\nThe Dashboard `mSearch` method was only used by the dashboard_picker and\nthis PR replaces its usage with the `search` method.\n\n### Identify risks\n\nThere is a slight risk in serverless environments where a browser may\nhave already loaded the dashboard_picker module but lags behind the\nserver. In this case, the dashboard picker may fail to retrieve a list\nof dashboards due to it calling the now non-existent `mSearch` method\nprovided by the server. In this case, the user simply needs to refresh\ntheir browser to retrieve the latest UI modules.","sha":"2a7e38b0fc3c33921f5a29f427bc3a6de8809c67"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210709","number":210709,"mergeCommit":{"message":"[Dashboard] Remove mSearch from content management (#210709)\n\n## Summary\n\nRemoves the mSearch method from Dashboard content management.\n\nThe `mSearch` content management method was designed to be a temporary\nimplementation of search that allowed searching multiple saved object\ntypes ([see more\n[internal]](https://docs.google.com/document/d/1ssYmqSEUPrsuCR4iz8DohkEWekoYrm2yL4QR_fVxXLg/edit?tab=t.0#heading=h.6sj4n6bjcgp5)).\nHowever, the mSearch implementation in the Dashboard Storage class lacks\nextensibility as it requires a synchronous `toItemResult` function. As\nwe start migrating reference handling to the server, we will likely need\ntransforms that return Promises (ex. `savedObjectToItem`), such as\n[retrieving tag saved objects from the SavedObjectTagging\nclient](https://github.com/elastic/kibana/issues/210619).\n\nThe Dashboard `mSearch` method was only used by the dashboard_picker and\nthis PR replaces its usage with the `search` method.\n\n### Identify risks\n\nThere is a slight risk in serverless environments where a browser may\nhave already loaded the dashboard_picker module but lags behind the\nserver. In this case, the dashboard picker may fail to retrieve a list\nof dashboards due to it calling the now non-existent `mSearch` method\nprovided by the server. In this case, the user simply needs to refresh\ntheir browser to retrieve the latest UI modules.","sha":"2a7e38b0fc3c33921f5a29f427bc3a6de8809c67"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
---|---|---|
.. | ||
bfetch_explorer | ||
content_management_examples | ||
controls_example | ||
data_view_field_editor_example | ||
developer_examples | ||
discover_customization_examples | ||
embeddable_examples | ||
error_boundary | ||
eso_model_version_example | ||
esql_ast_inspector | ||
esql_validation_example | ||
expressions_explorer | ||
feature_control_examples | ||
feature_flags_example | ||
field_formats_example | ||
files_example | ||
grid_example | ||
guided_onboarding_example | ||
hello_world | ||
locator_examples | ||
locator_explorer | ||
partial_results_example | ||
portable_dashboards_example | ||
preboot_example | ||
resizable_layout_examples | ||
response_stream | ||
routing_example | ||
screenshot_mode_example | ||
search_examples | ||
share_examples | ||
state_containers_examples | ||
ui_action_examples | ||
ui_actions_explorer | ||
unified_doc_viewer | ||
unified_field_list_examples | ||
user_profile_examples | ||
v8_profiler_examples | ||
README.asciidoc |
[[example-plugins]] == Example plugins This folder contains example plugins. To run the plugins in this folder, use the `--run-examples` flag (without a basepath), via [source,bash] ---- yarn start --run-examples ----