-
Notifications
You must be signed in to change notification settings - Fork 10
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
update RestHandler to provide an alternate URI path for actions #2994
Comments
davidnich
added a commit
that referenced
this issue
Sep 16, 2018
…at an "action=xxx" argument is not needed; instead the action can be added to the end of the URI path so that "PUT path/xxx" can be used instead of "PUT path?action=xxx"
davidnich
added a commit
that referenced
this issue
Sep 16, 2018
… match fails to avoid compatibility problems
davidnich
added a commit
that referenced
this issue
Sep 16, 2018
…s is not recommended; updated argument example
sejvlond
pushed a commit
that referenced
this issue
Sep 20, 2018
#2997) * refs #2994 Updated to support alternative URI paths for actions so that an "action=xxx" argument is not needed; instead the action can be added to the end of the URI path so that "PUT path/xxx" can be used instead of "PUT path?action=xxx" * refs #2994 only look for action methods for URI paths if the subclass match fails to avoid compatibility problems * refs #2994 improved docs; added a note that requiring action arguments is not recommended; updated argument example
davidnich
added a commit
that referenced
this issue
Sep 24, 2018
sejvlond
added a commit
that referenced
this issue
Sep 25, 2018
refs #2994 more consistent arugment handling for REST URI path action…
petrycta
pushed a commit
that referenced
this issue
Oct 10, 2018
#2997) * refs #2994 Updated to support alternative URI paths for actions so that an "action=xxx" argument is not needed; instead the action can be added to the end of the URI path so that "PUT path/xxx" can be used instead of "PUT path?action=xxx" * refs #2994 only look for action methods for URI paths if the subclass match fails to avoid compatibility problems * refs #2994 improved docs; added a note that requiring action arguments is not recommended; updated argument example
petrycta
pushed a commit
that referenced
this issue
Oct 10, 2018
davidnich
added a commit
that referenced
this issue
Jan 2, 2019
…atic lookups to be used everywhere in the REST hierarchy instead of just in the base handler object
davidnich
added a commit
that referenced
this issue
Jan 2, 2019
davidnich
added a commit
that referenced
this issue
Jan 2, 2019
davidnich
added a commit
that referenced
this issue
Jan 2, 2019
refs #2994 fixed issues related to improved method matching; allow st…
davidnich
added a commit
that referenced
this issue
Jan 2, 2019
davidnich
added a commit
that referenced
this issue
Jan 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
to be compatible with REST schemas such as Swagger / OAS
ex:
from:
instead of just:
PUT path?action=update
the following will also be supported:
PUT path/update
The text was updated successfully, but these errors were encountered: