CodeForPhilly / CodeForPhilly/stately
Would changing workflows corrupt previous cases?
- Dominant language
- Python
- Stars
- 22
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Right now when we modify workflows we dump and load, which also clears out the cases. Obviously in production we wouldn't want to do that. Eventually we'll even have a UI for modifying workflows. But if we, say, add a state to the end of the workflow, would that corrupt existing cases? What about modifying a state/action?
Just something to think about
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the current workflow dump/load operation and how it clears existing cases. Examine the impact of adding a state or modifying a state/action on stored cases; done means the compatibility behavior is defined and verified for these workflow changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100