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
We are encountering an issue with the enum constraint in the JSON schema. The constraint is case-sensitive, meaning that if we define the enum constraint with specific case-sensitive values, it will not accept variations in case. For example, if we define "enum": ["AMB"], it will not accept "amb" or "Amb".
Expected Behavior:
Is there an option to make the enum constraint case-insensitive, so that "AMB" would match "amb" or "Amb"?
The text was updated successfully, but these errors were encountered:
Overview
We are encountering an issue with the enum constraint in the JSON schema. The constraint is case-sensitive, meaning that if we define the enum constraint with specific case-sensitive values, it will not accept variations in case. For example, if we define "enum": ["AMB"], it will not accept "amb" or "Amb".
Expected Behavior:
Is there an option to make the enum constraint case-insensitive, so that "AMB" would match "amb" or "Amb"?
The text was updated successfully, but these errors were encountered: