You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, if a user attempts to add an allowed spec on the InteractionBlockingInterceptor that's listed as 'search' or 'history', it will return an unknown interaction, despite both these specs being part of the code system that these specs are based off of.
To Reproduce
Steps to reproduce the behavior:
Attempt to add an allowed spec with the definition 'search' or 'history'
Expected behavior
'search' & 'history' should be allowed operations for the InteractionBlockingInterceptor, which should include their sub-operations.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, if a user attempts to add an allowed spec on the InteractionBlockingInterceptor that's listed as 'search' or 'history', it will return an unknown interaction, despite both these specs being part of the code system that these specs are based off of.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
'search' & 'history' should be allowed operations for the InteractionBlockingInterceptor, which should include their sub-operations.
The text was updated successfully, but these errors were encountered: