-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[8.9] Add ESRE landing page sections #159809
[8.9] Add ESRE landing page sections #159809
Conversation
…-ref HEAD~1..HEAD --fix'
pageHeader={{ | ||
pageTitle: i18n.translate('xpack.enterpriseSearch.esre.guide.pageTitle', { | ||
defaultMessage: 'Enhance your search with ESRE', | ||
}), | ||
}} | ||
> | ||
<SetPageChrome /> | ||
<p>ESRE placeholder</p> | ||
<EuiPanel color="transparent" paddingSize="none"> |
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.
I decided to use EuiPanel
instead of <EuiPageTemplate.Section>
. I had issues with padding when using the latter (for example the header is wider than the sections).
...ns/enterprise_search/public/applications/esre/components/esre_guide/esre_guide_accordion.tsx
Outdated
Show resolved
Hide resolved
import { MeasurePerformanceSection } from './measure_performance_section'; | ||
import { RankAggregationSection } from './rank_aggregation_section'; | ||
import { SemanticSearchSection } from './semantic_search_section'; | ||
|
||
export const EsreGuide: React.FC = () => { |
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.
I'm not sure what logic I should cover with unit tests; everything in this PR is using EUI components. Maybe I can add a test that <EsreGuide>
renders the custom sections. Thoughts?
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.
I think you're good for now. We will sometimes test components with enzyme, but usually only if there is complex logic controlling rendering.
We also want to start using react-testing-library instead of enzyme for this kind of testing.
@elasticmachine merge upstream |
...ugins/enterprise_search/public/applications/esre/components/esre_guide/esre_docs_section.tsx
Outdated
Show resolved
Hide resolved
...ns/enterprise_search/public/applications/esre/components/esre_guide/esre_guide_accordion.tsx
Outdated
Show resolved
Hide resolved
...ns/enterprise_search/public/applications/esre/components/esre_guide/esre_guide_accordion.tsx
Show resolved
Hide resolved
...ns/enterprise_search/public/applications/esre/components/esre_guide/esre_guide_accordion.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/enterprise_search/public/applications/esre/components/esre_guide/esre_guide.tsx
Outdated
Show resolved
Hide resolved
...ugins/enterprise_search/public/applications/esre/components/esre_guide/esre_docs_section.tsx
Outdated
Show resolved
Hide resolved
...ns/enterprise_search/public/applications/esre/components/esre_guide/esre_guide_accordion.tsx
Outdated
Show resolved
Hide resolved
...rprise_search/public/applications/esre/components/esre_guide/measure_performance_section.tsx
Outdated
Show resolved
Hide resolved
...rprise_search/public/applications/esre/components/esre_guide/measure_performance_section.tsx
Outdated
Show resolved
Hide resolved
@TattdCodeMonkey @sphilipse I've addressed your comments. |
…com/demjened/kibana into demjened/esre-landing-page-sections
import { MeasurePerformanceSection } from './measure_performance_section'; | ||
import { RankAggregationSection } from './rank_aggregation_section'; | ||
import { SemanticSearchSection } from './semantic_search_section'; | ||
|
||
export const EsreGuide: React.FC = () => { |
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.
I think you're good for now. We will sometimes test components with enzyme, but usually only if there is complex logic controlling rendering.
We also want to start using react-testing-library instead of enzyme for this kind of testing.
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Unknown metric groupsESLint disabled line counts
miscellaneous assets size
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
## Summary This PR follows #159809 and adds content to the expandable accordion sections. The 1st accorion (ELSER) is open by default on page visit. We're also adding links in the sections, which point to documentation or to internal Kibana pages (e.g. Behavioral Analytics, Trained Models). New entries are being added to the doc links files. ![ESRE_panels](https://github.com/elastic/kibana/assets/14224983/a50c5705-0192-4a86-8444-9d4b1a9859b2) ### Checklist - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [x] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [x] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Summary
This PR continues #159589 and adds 4 sections to the ESRE landing page, with a few caveats - these will be addressed in subsequent PRs:
Checklist