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
[Ent Search] Update Playground copy #181951
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
x-pack/plugins/search_playground/public/components/edit_context/edit_context_flyout.tsx
Show resolved
Hide resolved
thanks for those updates! |
<p> | ||
<FormattedMessage | ||
id="xpack.searchPlayground.startNewChat.description" | ||
defaultMessage="Combine your Elasticsearch data with the power of large language models for retrieval augmented generation (RAG). Use the UI to view and edit the Elasticsearch queries used to search your data, then download the code to integrate into your own application." |
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.
@julianrosado for your eyes only
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.
Looks... good to me. :: Nod ::
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.
LGTM
@@ -40,7 +40,7 @@ export const CreateIndexCallout: React.FC = () => { | |||
<p> | |||
<FormattedMessage | |||
id="xpack.searchPlayground.sources.createIndexCallout.description" | |||
defaultMessage="You can not continue without having at least one index with data to search." | |||
defaultMessage="You need at least one index with data to search. " |
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.
nitpik: Is the last space intentional?
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
(cherry picked from commit 7fa867c)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `8.14`: - [[Ent Search] Update Playground copy (#181951)](#181951) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Liam Thompson","email":"32779855+leemthompo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-04-29T15:54:05Z","message":"[Ent Search] Update Playground copy (#181951)","sha":"7fa867cdd70251b30e007888840a66ccd5f57098","branchLabelMapping":{"^v8.15.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.14.0","v8.15.0"],"title":"[Ent Search] Update Playground copy","number":181951,"url":"#181951 Search] Update Playground copy (#181951)","sha":"7fa867cdd70251b30e007888840a66ccd5f57098"}},"sourceBranch":"main","suggestedTargetBranches":["8.14"],"targetPullRequestStates":[{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.15.0","branchLabelMappingKey":"^v8.15.0$","isSourceBranch":true,"state":"MERGED","url":"#181951 Search] Update Playground copy (#181951)","sha":"7fa867cdd70251b30e007888840a66ccd5f57098"}}]}] BACKPORT--> Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Number of changes discussed with @joemcelroy and @julianrosado. I've made a few tweaks based on how stuff looks.
Text for the main overview:
TODO
xpack.searchPlayground.editContext.flyout.description
Can just link to existing Playground doc link.