Buggy dashboard schema validator

See screenrecording. I briefly remove a field and add it back in but I still see errors

11 Replies

Thanks for posting in <#1088161997662724167>. Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets. - Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.) - Use search.convex.dev to search Docs, Stack, and Discord all at once. - Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI. - Avoid tagging staff unless specifically instructed. Thank you!

David AlonsoOP•4mo ago

is there a way I can reset to the old approach? where it still lets me press save? Our schemas make use of pretendWithConstraint helpers that allow us to store different types of objects inside fields within some constraints while type checking to specific types. The ability to edit and attempt to save in the dashboard was a very convenient way for us to test this but now we can't anymore..

David AlonsoOP•4mo ago

for now i created a dummy helper mutation to help with this but it would be great to fix this soon!

ari•4mo ago

Hey David, thanks for the report. I'm going to turn schema validation on the dashboard off for the weekend and take a look on monday

David AlonsoOP•4mo ago

Thanks, happy to share more if you need it

ari•4mo ago

If you could share the part of the schema that caused this problem that would be helpful to debug!

David AlonsoOP•4mo ago

okay, I'll try to get back to you I'm making a lot of changes to the schema so not sure what version exactly broke this but I'm pretty sure it has to do with the fact that I'm using this helper

export const pretendWithConstraint = <
  T extends GenericValidator,
  C extends GenericValidator,
>(
  _typeToImmitate: T,
  constraint: C
): T => constraint as unknown as T;

export const pretendWithConstraint = <
  T extends GenericValidator,
  C extends GenericValidator,
>(
  _typeToImmitate: T,
  constraint: C
): T => constraint as unknown as T;

ari•3mo ago

Hm, I'm not familiar with that helper. Is it something you wrote? Are there unions in your schema?

David AlonsoOP•3mo ago

Yep tons of unions Yeah i wrote that helper

ari•3mo ago

Thanks for confirming, I've gotten another report of certain unions causing issue with schema validation, but haven't been able to reproduce yet. Would you be open to clicking "Show Schema" on the bottom-left of the data page and sharing that code with me (feel free to dm)? Then I can add a new tests case for the type of union you have 🙂 Hey David, we identified the edge case causing you to see the error from before. I turned the schema validation feature back on for you, so you should start seeing validation errors when your types don't match your schema, but they should now only appear when there is truly a validation error. Please let me know if you see otherwise

David AlonsoOP•3mo ago

seems to be working again!