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.
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.
In the provided code snippet, there is an issue with duplicate rules defined for the
content_listfield. Specifically, you have two instances of the same rule:This will cause validation errors because rules should be unique within a component's
rulesobject.Additionally, the order of these lines might not meet your expected logic. If both fields need to be validated and are required, they should likely share the same validation rule.
Here is improved version of the rule definition:
:rules="{ content_list: [ { message: $t('views.applicationWorkflow.nodes.textToSpeechNode.content.label'), trigger: 'change' }, { required: true } ] }"Explanation:
content_list.{}instead of single quotes around the array to avoid syntax errors in Vue templates.These changes ensure that the form checks the value change on
content_list, and if it’s empty (not valid according to$t('views.applicationWorkflow.nodes.textToSpeechNode.content.label')), then also considers it as invalid due torequired: true`.