Workflow introspection missing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 109
- Forks
- 107
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 4
Description
Not a direct feature request but a common observation in working with plone.restapi:
Using the @workflow endpoint requires knowledge about the underlying workflow and its transitions.
In particular with custom workflows, it is very hard to write custom code for bringing a particular object into a particular workflow state (e.g. as part of a migration).
Perhaps two options:
- allow introspection on all workflows
- perhaps useful: some way to set the workflow state and the related object security directly (as asked in my question https://community.plone.org/t/setting-review-state-quick-programmatically/12991)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the @workflow endpoint and the linked community question about setting review state programmatically. Compare the two proposed directions—introspection of all workflows or direct workflow-state and security updates—and establish which behavior the issue should deliver. Done should include an agreed scope and an API design for custom workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100