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
Because the operation is not using a template, all emitters are treating the property as if there is no @key.
Therefore in the client side test cases, we do not even have a way to put the id into the request - the path does not have that parameter, and in body, it has visibility("read") therefore it should not appear in the body.
Now we have a very weird situation that the server is expecting the id value, but on the client side, we have no way to put it into the request.
The text was updated successfully, but these errors were encountered:
There are a few use cases of
@key @visibility("read")
forid
property in the create body in todoApp spec, for example:typespec-e2e-demo/todoApp/spec/main.tsp
Line 21 in ae71e18
typespec-e2e-demo/todoApp/spec/main.tsp
Line 46 in ae71e18
Because the operation is not using a template, all emitters are treating the property as if there is no
@key
.Therefore in the client side test cases, we do not even have a way to put the
id
into the request - the path does not have that parameter, and in body, it hasvisibility("read")
therefore it should not appear in the body.Now we have a very weird situation that the server is expecting the
id
value, but on the client side, we have no way to put it into the request.The text was updated successfully, but these errors were encountered: