-
Notifications
You must be signed in to change notification settings - Fork 112
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
PUT behavior is not setting Defaults when replacing item #226
Comments
Try making that field |
Required and Default sounds like excluding attributes to me, because if the field is required to be provided, the default value should never be used, right? However, I tried to setup both attributes and this is how it went;
Seems that it's working, but its confusing that field are not really required, even on a POST statement :)
I think that enabling the Required attribute to all those that have Default should fix my issue. Thanks! |
Yeah, I am thinking the same, as we are missing something with these qualifiers. We are open for discussions and ideas how to fix these. Discussion at #174. |
@apuigsech Should we close this, or you have something to add? |
We can close it :) |
I am trying to fix an issue I found on the SQL Storage Handler (apuigsech/rest-layer-sql#1) and I was able to fix it just partially because seems that REST Layer is not considering some Schema attributes, as the Default, when a PUT is done to replace an element.
Next lines shows how the default value (0 on the 'int' field) is setup when creating the object but not when replacing it;
The text was updated successfully, but these errors were encountered: