Closed ai closed 1 month ago
Don’t rush. Check all changes in PR again.
Run pnpm test
.
Think about changing documentation.
scripts/
, add a comment with a description.README.md
.Think about code testing.
If you added a new dependency, check our requirements.
Think about moving code to core/
. What code will also be useful on other platforms?
Think about HTML semantics.
Think about accessibility. Try to search for a11y recommendations for your case. Think about how screen reader users will use the tool. Is it easy to use on a screen with bad contrast?
The UI was checked in Chrome and Firefox (and Safari or Epiphany if you have them).
Since you’ve made changes to files in web/main/
consider these points:
web/public/404.html
or web/public/500.html
?index.html
.Think about making types more precise. Can you better explain data relations by type?
node
now can strip TS types natively..js
to.ts
better-node-test
with this feature supportnode
with right argument and without experimental warnings