More the /api/v1/workflow/FIRE methods to content api
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
User Story
It is odd to use the workflow API when managing content. It seems like the workflow API should focus on managing workflows and the content api on managing content.
To that end, we should copy all the workflow/fire methods to the api/v1/content endpoint so they can be more easily discovered and used.
Acceptance Criteria
Move the workflow fire endpoints that push content to the content api endpoint.
Proposed Objective
Please Select
Proposed Priority
Please Select
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
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 by locating the existing api/v1/workflow/FIRE endpoints and the api/v1/content entry point, then compare which fire methods push content. The work is done when those content-related workflow fire endpoints are available through the content API without removing the intended behavior from workflow management.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100