docs: update unit-tests.md#303
Conversation
| }); | ||
| ``` | ||
|
|
||
| ### DB helper functions |
There was a problem hiding this comment.
Again here, instead of dumping code that without context is meaningless, explain why the code is here, the pattern it represents, how the pattern is used in code, and when the person should use that pattern
| }); | ||
| ``` | ||
|
|
||
| > Note: Each test runs with **isolated storage** (enabled by default). Writes are undone after the test, so ordering is reliable. |
There was a problem hiding this comment.
issue: This should be more proeminent information and not a footnote. It completely changes how a user should think about the tests.
Co-authored-by: Marco Campos <me@madcampos.dev>
Deploying volunteer with
|
| Latest commit: |
9e665ed
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1d4f07d0.volunteer-ekr.pages.dev |
| Branch Preview URL: | https://docs-unit-test.volunteer-ekr.pages.dev |
There was a problem hiding this comment.
After reading the text a second time, it sounds too much like AI slop.
The text is hollow and dry, in a bad way. Yes, it explains what things are and what they do, but it does so in a way a dictionary would do it, flat, empty, and without intentionality.
The documentation for a project should convey the reasoning for the decisions, the tradeoffs, the whys!
Please rewrite it yourself, with your own words, or if you use any LLM to write something review and edit it. Add your voice.
In the end of the day, any person can use an LLM and generate very decent text the same way, regardless of knowledge or life journey. Your voice is unique though, use it.
2 participants
No description provided.