Index pattern creation - text improvements#107860
Conversation
gchaps
left a comment
There was a problem hiding this comment.
++ to index alias
Can you please provide screenshots that shows the latest for these two messages. I'd like to see how the final text looks.
-
The index pattern you entered doesn't match any indices. You can match 1 index below.
-
Your index pattern doesn't match an indices, but you have an index that looks similar.
...ugins/index_pattern_editor/public/components/preview_panel/status_message/status_message.tsx
Outdated
Show resolved
Hide resolved
...ugins/index_pattern_editor/public/components/preview_panel/status_message/status_message.tsx
Outdated
Show resolved
Hide resolved
...ugins/index_pattern_editor/public/components/preview_panel/status_message/status_message.tsx
Outdated
Show resolved
Hide resolved
|
@gchaps Here are your requested screenshots - |
|
A few comments: Is this hint text still correct. It only mentions indices. Or should it be "to match multiple sources" or "to match multiple characters" It seems to me that a word is needed after the number 1. Does this work: Your index pattern doesn't match any data streams, indices, or index aliases, but 1 source is similar. How about this: No data streams, indices, or index aliases match your index pattern. You can match 1 source. |
|
Pinging @elastic/kibana-app-services (Team:AppServices) |
|
@elasticmachine merge upstream |
gchaps
left a comment
There was a problem hiding this comment.
LGTM. Thanks for updating the text.
💚 Build SucceededMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: |
* text improvements
💚 Backport successful
This backport PR will be merged automatically after passing CI. |







Summary
Minor text improvements in follow up to #101853
Its worth noting that I tried to standardize around
index aliasinstead of justaliasas its a searchable technical term but if I'm causing trouble I'm happy change course.