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
TrainingData.merge() doesn't check for duplicate examples per intent #1446
Comments
just when merging? do even check for duplicates within an intent? |
You're right, there's nothing implemented. The only data processing done for the intents upon building |
@MetcalfeTom is this still relevant? |
It is still relevant for features like interactive learning where we dump new NLU data. I think it functions well as a community issue |
I want to work on this |
awesome! let us know if we can help with anything |
@akelad what would the unit test using @MetcalfeTom example look like? Should I create a markdown file containing the given examples or can each intent be represented as an instance of |
@hsm207 you can take a look at the tests written here: https://github.com/RasaHQ/rasa/blob/master/tests/nlu/base/test_training_data.py |
See issue RasaHQ#1446 for details.
Rewrite test_markdown_entity_regex() because the training_examples in TrainingData no longer maintains the order of the list of messages passed to its constructor after sanitization.
This reverts commit 0330f26.
@akelad This issue can be closed now. |
e.g. by merging
with
we get
The text was updated successfully, but these errors were encountered: