lambdaclass / lambdaclass/guidelines
Add a rule about error, exits and exceptions in Erlang
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
@juanbono @hernanex3 if you find the discussion we have about this some time ago, please paste it here so we can extract a rule out of it.
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 names no files or tests. Start by locating the earlier discussion about Erlang errors, exits, and exceptions referenced in the issue, then extract the agreed guidance. Done means the discussion has been resolved into a clear rule in the guidelines repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100