Add interface to set default "initial state" for a job
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When a job is created/edited, the user should be able to setup an arbitrary initial state by selecting global dataclips and assigning them to certain keys in state.
N.B. that certain keys may get overwritten by assemble_state - specifically anything put in data and configuration is unsafe.
Thereafter, the job may be triggered manually or may be triggered using the default state. If the job has never run before, it will use the default state.
Note: this is blocked by "run job with arbitrary dataclip"
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing job creation/editing flow and the separate "run job with arbitrary dataclip" issue, which blocks this work. Trace how manual triggers and first runs currently choose state, then confirm that the configured dataclips populate the initial state while data and configuration remain unsafe to rely on. Done means the interface supports assigning global dataclips to state keys and a never-run job uses that default state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100