Closed ZhuQinglei closed 6 years ago
There is no obvious issue here. Please create a minimal reproduction app and post a link to the repo if you still need help with this.
Have you had the index on this property for long and now just changed the unique
boolean? See #19 for details.
@aldeed I am having problem to get the
notUnique
error at all. Here is my code for schema (the collection is placed in imports folder and imported to client and server side respectively, so both client and server shares the same collection schema code):Here is my code for mapping error message for displaying on client side:
and I can find the document with the same name as shown below, so it should add the error to the current context.
But I did not see the unique error in my validation errors as there are only 5 errors without the expected
notUnique
error:So it is not displayed on the screen as well, where all the other error messages are correct:
Do you know why it is behaving like this?