Skip to content
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

Closed
davidnich opened this issue Sep 15, 2018 · 0 comments
Closed

update RestHandler to provide an alternate URI path for actions #2994

davidnich opened this issue Sep 15, 2018 · 0 comments

Comments

@davidnich
Copy link
Contributor

davidnich commented Sep 15, 2018

to be compatible with REST schemas such as Swagger / OAS

ex:
from:

hash<auto> putUpdate(hash<auto> cx, *hash<auto> ah) {
    # ...
}

instead of just:
PUT path?action=update

the following will also be supported:
PUT path/update

@davidnich davidnich added this to the 0.9 milestone Sep 15, 2018
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
davidnich added a commit that referenced this issue Sep 16, 2018
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 21, 2018
davidnich added a commit that referenced this issue Sep 23, 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
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
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
davidnich added a commit that referenced this issue Jan 3, 2019
* refs #2994 fixed comments in RestHandler

* refs #2994 do not move the default get handler to AbstractRestClass - leave it in RestHandler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant