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
Make
rasa data validate
check for duplicated intents, forms, responses and slots when using domains split between multiple files #10444Make
rasa data validate
check for duplicated intents, forms, responses and slots when using domains split between multiple files #10444Changes from 8 commits
1c32d91
48b5e00
f83c927
c4adecd
9e065f3
b1f47a9
46311f6
bdd3f79
1512830
8518d07
75aaded
0235404
718cae1
96e7d25
03d88ea
c5e755b
bca3f45
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.
Did we consider just raising an error/warning here so that we don't need to store the duplicates on the class?
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.
The idea was to show this information only when running
rasa data validate
, as it's written in the description of this issue. We can update it to show the warning every time the domain is getting merged but in this case I don't see the point in doing any changes torasa data validate
and even link this issue to the validator which means the whole task will be different.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.
Maybe @TyDunn can take a look at it and say which approach we prefer.
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.
Does the approach that @joejuzl describe happen when you run
rasa data validate
too?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.
@TyDunn If we do it the way @joejuzl proposes then the warnings/exceptions will be raised every time the domain is getting merged (e.g. when just running rasa train or literally any other command that uses domain), not only when doing
rasa data validate
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.
For context we do already have quite a lot of domain validation that happens just from loading it e.g.
_check_domain_sanity
in the__init__
looks for duplicates etc.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.
@alwx I believe Joe is out for the rest of the year, and I am not going to be able to gain enough context atm. Can you make a judgement call here yourself?
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.
@TyDunn I think it makes sense to keep this one as it as and maybe create a new issue because what Joe was talking about makes the scope much bigger