Typechecking documentation shows wrong .check output
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 379
- Avg merge
- 14m
- Merged PRs (30d)
- 8
Description
The first query check (the one where there are issues) in
https://tpolecat.github.io/doobie/docs/06-Checking.html
(/modules/docs/src/main/tut/docs/06-Checking.md)
returns the same output as the second one (the one where issues are fixed).
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
Open /modules/docs/src/main/tut/docs/06-Checking.md and compare the first query-check example with the second one, then inspect the rendered Checking documentation. The first example should show the output for a query with issues, while the second should show the output after those issues are fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100