-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support ECProperty value range #779
Support ECProperty value range #779
Comments
@ColinKerr, while I totally agree that editors should respect these attributes for users' convenience, I also think that ECDb should make sure to validate values against them as well. |
@FelixGirard, we can enforce the values, but we were wondering how and when do you expect for users to be notified about the constrains?
|
Honestly I just wanted them to be enforced, I was thinking just putting them in the html attributes for the inputs. |
ECProperty supports adding constraints to values.
https://www.itwinjs.org/bis/ec/ec-property/#additional-optional-attributes
These are not enforced by the ECDb.
They should be enforced by the inputs in the property grid.
To query those, you can use the meta.ECPropertyDef table
The text was updated successfully, but these errors were encountered: