-
Notifications
You must be signed in to change notification settings - Fork 362
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
Property formatters, constraints #128
Comments
@bajtos @ritch @raymondfeng I believe that the docs are incorrect, as I cannot find any references in the source code (of datasource-juggler and loopback itself) regarding:
I would have expected the constraints to add the right validations. Additionally, you'd expect a property with type=number to apply validatesNumericalityOf and so forth. ConstraintsConstraints are modeled as options too, for example:
Conversion and formattingFormat conversions can also be declared as options, for example:
|
We need to enhance the property handling to support the attributes for constraints and conversions. |
👍 |
@raymondfeng Seems like this has been open a while -- shouldn't this be removed from the documentation in loopback? It caused me a lot of grief yesterday |
@raymondfeng This should definitely be remove from docs. |
I "commented out" that section from http://docs.strongloop.com/display/LB/Model+definition+JSON+file, so it won't be visible to general viewers. Sorry it caused problems. Please mention or comment on strongloop/loopback#523 when this issue is fixed so I add the docs back once it actually works. |
hello from the other side!! this feature would be really helpful, i guess. looking forward to your updates. thanks. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
Where does the actual implementation of property formatters (trim, uppercase, ...) come from? Is it provided by a connector (or a database engine itself)? I could not find any references in-code, and it'd be interesting to be able to provide your own formatters (like urlify/slugify for example).
The text was updated successfully, but these errors were encountered: