Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Security Solution] Update prebuilt rule customization UI copy #210817
[Security Solution] Update prebuilt rule customization UI copy #210817
Changes from 5 commits
cbad2dc
a36b921
a5cc303
7e87ccb
4c54e9e
9056239
e7ec786
4ff7724
a5e7503
f010a93
013bf50
b480a1c
03347e1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we want to indicate why the field(s) aren't editable, as the copy did previously? I don't see any EUI recommendation recommendation explicitly for reasoning, but it feels like more context here might be helpful to the user.
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.
Nastasha's idea was to make these messages more generic and more reusable. But now as you brought this up, I think it might be a good idea to be just a bit more specific, like: "This field is not editable for Elastic rules". Or maybe we can even pass in the name as a parameter to avoid having multiple translation strings.
wdyt, @nastasha-solomon?
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.
Sorry, just getting to this now. That's a valid point, @rylnd. Changing the language to what @nikitaindik suggested should remove the ambiguity.
@nikitaindik either of your suggestions work. I'd just make some minor adjustments:
<field name>
can't be edited for Elastic rules.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.
Thanks for you suggestions, folks! Pushed an update.