on 03-23-2020 12:22 PM
Dear CAP Team,
Not sure whether it is a bug or a feature: When I'm sending PUT requests to update virtual fields or fields annotated with @readonly, updating is not happening (correct!), but the response status is 200 OK
. So, the http client gets no indication that he is trying to work against the model. (cds version 3.31.2 on Node.js). The response body shows 'null' as value of such fields. The client needs to compare request and response to figure out that something didn't work as expected.
I would consider such request to result in an error, but I don't know what others think about it ... ?
Klaus
Hi Klaus,
Personally I also would expect errors, however according to the OData specification those fields are just ignored. So the runtime behaviour is correct.
Best regards,
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I think CAP should change this OData standard behaviour.
One possible solution could be adding a new parameter in cds config:
runtime: {
newParam: false
}
Best
Alice
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.