We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Commit: f377cda
-- In Django Swagger:
Workflow API2 allows all CRUD actions, unprotected.
Which actions do we require?
The text was updated successfully, but these errors were encountered:
@hackdna @ngehlenborg @scottx611x : It doesn't appear the front end is using this API, but I could be mistaken. Please comment on the expected behavior.
Sorry, something went wrong.
The only allowed operation for APIs by default should be a GET.
I've gotten rid of the Workflow API v2 in one of my recent branches. We should have some discussion if it's worth keeping/upgrading it to DRF.
Can you please clarify why you would want to get rid of the API?
@nils sure, the api was updated to DRF to support a feature that never came into fruition. I believe #866
I figured if we are not working on this feature I could reimplement the v2 API once #866 comes back into the loop
scottx611x
No branches or pull requests
Commit: f377cda
Steps to reproduce
-- In Django Swagger:
or
https://refinery-dev.stemcellcommons.org/docs/#!/workflows/Workflow_list
Observed behavior
Workflow API2 allows all CRUD actions, unprotected.
Expected behavior
Which actions do we require?
The text was updated successfully, but these errors were encountered: