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
When a user deletes a classifier, the deleted classifier is still displaying on the list and when focused server error message is displayed. To Reproduce
Steps to reproduce the behaviour:
Go to 'Mauro'
Click on 'a Classifications menu
Delete a classifier
The deleted classifier is still displaying on the list. Expected behaviour
The deleted classifier should not be on the list as it is expected to disappear online/realtime
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
The issue is that the Classification list is not responding to the event of the classifier being deleted. A full page reload shows that the classifier has been removed though.
Describe the bug
When a user deletes a classifier, the deleted classifier is still displaying on the list and when focused server error message is displayed.
To Reproduce
Steps to reproduce the behaviour:
Go to 'Mauro'
Click on 'a Classifications menu
Delete a classifier
The deleted classifier is still displaying on the list.
Expected behaviour
The deleted classifier should not be on the list as it is expected to disappear online/realtime
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: