Julia Rechkunova 8d399fe3aa [UnifiedFieldList] Remove redundant server routes. Create new example plugin for unified field list components and migrate tests. (#158377) ... - Closes https://github.com/elastic/kibana/issues/147885 - Closes https://github.com/elastic/kibana/issues/157109 ## Summary **Before:** Unified Field List plugin has internal routes (wrappers for client code) which exist only to run api functional tests against them: - `/api/unified_field_list/existing_fields/{dataViewId}` - `/api/unified_field_list/field_stats` Client code does not call these routes directly. So there is no reason in keeping and versioning them. **After:** - Internal routes are removed - A new "Unified Field List Examples" page was created http://localhost:5601/app/unifiedFieldListExamples - API functional tests (which used the routes) were converted to functional tests against this new example page - Created a new `unifiedFieldList` page object which is used now in functional tests (methods are extracted from existing `discover` page object). **For testing:** Steps: 1. Run Kibana with examples: `yarn start --run-examples` 2. Install sample data 3. And navigate to Developer Examples > Unified Field List Examples page.  ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>		2023-05-31 13:25:47 +02:00
..
index.ts	[UnifiedFieldList] Remove redundant server routes. Create new example plugin for unified field list components and migrate tests. (#158377)	2023-05-31 13:25:47 +02:00