kibana/x-pack/plugins/enterprise_search
Scotty Bollinger 5beb47a1f7
[Workplace Search] Migrate additional shared source components (#83850)
* Initial copy/paste of components

Changes for pre-commit hooks were:

- Linting
- Lodash imports
- remove `any` type in favor of React.ReactNode
- Move setState to top of component

* Add image

* Update component paths

* Remove reference to ConfirmModal

Since all the legacy component does it wrap the EUI component we decided to drop it.

Legacy:
https://github.com/elastic/ent-search/blob/master/app/javascript/shared/components/ConfirmModal/ConfirmModal.tsx

* Remove local flash messages in favor of global flash messages

* Various type fixes

* Fix image location
2020-11-19 16:43:18 -06:00
..
common [bundle optimization] Update to semver 7.x to get tree-shaking (#83020) 2020-11-14 07:32:02 -05:00
public [Workplace Search] Migrate additional shared source components (#83850) 2020-11-19 16:43:18 -06:00
server Removing circular dependency between spaces and security (#81891) 2020-11-19 13:41:13 -05:00
kibana.json Removing circular dependency between spaces and security (#81891) 2020-11-19 13:41:13 -05:00
README.md [Enterprise Search] Update CODEOWNERS and README (#78809) 2020-09-29 11:44:07 -07:00

Enterprise Search

Overview

This plugin's goal is to provide a Kibana user interface to the Enterprise Search solution's products (App Search and Workplace Search). In it's current MVP state, the plugin provides the following with the goal of gathering user feedback and raising product awareness:

  • App Search: A basic engines overview with links into the product.
  • Workplace Search: A simple app overview with basic statistics, links to the sources, users (if standard auth), and product settings.

Development

  1. When developing locally, Enterprise Search should be running locally alongside Kibana on localhost:3002.
  2. Update config/kibana.dev.yml with enterpriseSearch.host: 'http://localhost:3002'
  3. For faster QA/development, run Enterprise Search on elasticsearch-native auth and log in as the elastic superuser on Kibana.

Kea

Enterprise Search uses Kea.js to manage our React/Redux state for us. Kea state is handled in our *Logic files and exposes values and actions for our components to get and set state with.

Advanced Kea usage

For the most part, we stick to the functionality described in Kea's core concepts. However, in some files, we also take advantage of props and events, as well as manually mounting some shared logic files on plugin init outside of React.

Debugging Kea

To debug Kea state in-browser, Kea recommends Redux Devtools. To facilitate debugging, we use the path key with snake_cased paths. The path key should always end with the logic filename (e.g. ['enterprise_search', 'some_logic']) to make it easy for devs to quickly find/jump to files via IDE tooling.

Testing

Unit tests

From kibana-root-folder/x-pack, run:

yarn test:jest plugins/enterprise_search

E2E tests

See our functional test runner README.