LispCookbook / LispCookbook/cl-cookbook
Would it be useful open a new chapter for common error for new lispers?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 158
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 2
Description
I think it would probably be helpful to open a new chapter which collects common error & problems for new lispers. What do you say?
I think it may save time from debugging & googling if we could make something that can auto detect universal error and show common solutions from a db.
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
The issue proposes a new chapter for common errors and an auto-detection system backed by a database, but names no files, tests, or entry points. First define the scope and requirements with maintainers; done would be an agreed direction for the chapter and whether the automated system belongs in this cookbook.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100