If the intent was matched and called the intent should be able to reject itself so the understanding will go to the next match automatically.
For example "add utility" matches utility first, but it gets rejected because it doesn't match the "must" via the understanding in training. Then it uses the next in the list calculator, because it found the word "add" and changed it to "+ utility".
At this point calculator should be able to reject this.
Maybe it could use this.reject();
Needs an example to be built with two intents, maybe PingPing intent.
"ping ping" -> rejects(); so it'll end up with "ping" intent
"ping PING" -> is handled, returns "ping ping ping pong?"
If the intent was matched and called the intent should be able to reject itself so the understanding will go to the next match automatically.
For example "add utility" matches utility first, but it gets rejected because it doesn't match the "must" via the understanding in training. Then it uses the next in the list calculator, because it found the word "add" and changed it to "+ utility".
At this point calculator should be able to reject this.
Maybe it could use this.reject();
Needs an example to be built with two intents, maybe PingPing intent. "ping ping" -> rejects(); so it'll end up with "ping" intent "ping PING" -> is handled, returns "ping ping ping pong?"
This could also be related to intent validators.