camunda / camunda/api-test-generator
Awareness: readback after mutation with no semantic types
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 3
- Avg merge
- 13h 41m
- Merged PRs (30d)
- 23
Description
Logging for future awareness.
While implementing #305, we implemented #309 to allow "readback after mutation" to prove that the mutation held.
Turns out that at least updateUserTask takes no semantic types in the changeset, so these have to be synthesized.
The mutated fields likewise have no semantic types in getUserTask.
So we are correlating them by matching on name.
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
Review issues #305 and #309, then inspect how updateUserTask and getUserTask expose semantic types. The issue does not name files, tests, or a concrete acceptance condition, so the required behavior and definition of done need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100