Async (de)serialization
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 99
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 17
Description
No concrete API proposal yet, but we need a place to discuss the best way to handle async serialization/deserialization within devalue. This is most useful for promises, but it might also be good to be able to serialize streams/async iterables
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
No concrete API proposal, file, test, or entry point is provided. Start by reviewing devalue's existing serialization and deserialization behavior, then compare requirements for promises, streams, and async iterables. Done means reaching agreement on a concrete async API and its supported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100