Replies: 1 comment 3 replies
-
I'm not sure this is doable, the URI variables are place holders for URI variables that have a different encoding to JSON and are used to match the request in the most efficient way possible. It would add significant performance overhead if you request matching had to start parsing the request body. I am moving this to a discussion of ideas for the moment. Thoughts @jameskleeh ? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
currently this wont work:
leads to:
error: The route declares a uri variable named [note.docEntry], but no corresponding method argument is present
instead this is needed:
so I suggest to let it access inner properties of objects as it leads to smaller and cleaner code, especially when working with OData services/ web services that need a part of the body also in their path
Beta Was this translation helpful? Give feedback.
All reactions