Fallback to implicit serialization for diagram operations
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The implementation of dynamic workflows in #27 requires users to explicitly register which operations their type is able to do.
For types that can be both serialized and deserialized, it should be possible to support all operations by falling back on their serialized forms, even if the user did not explicitly register compatibility with the operation.
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 reading the dynamic-workflow implementation from #27 and trace how operation compatibility is registered. Determine how serialized and deserialized forms are represented; done means types supporting both can perform all diagram operations without explicit compatibility registration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100