consider making Type.Messages somehow nestable so that dependent typing information can be communicated
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 110
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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
The issue provides no file, test, or implementation details beyond Type.Messages and the goal of nesting dependent typing information. Start by locating Type.Messages and reading its current representation and related tests, if present. Done would require an agreed design and tests showing nested messages communicate the dependent typing information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100