Break down your files and learn what's inside. Created by Evan Hahn.
Go to file
Evan Hahn fbdf529257 Add a "code style" section to the readme 2023-08-02 13:24:29 -05:00
public PNG: Update styling; slightly usable now 2023-08-02 12:35:48 -05:00
test PNG: parsing PNG data 2023-08-02 11:43:02 -05:00
types PNG: very basic UI skeleton 2023-08-02 12:25:42 -05:00
README.md Add a "code style" section to the readme 2023-08-02 13:24:29 -05:00
deno.json PNG: basic skeleton 2023-08-01 09:20:57 -05:00
deno.lock PNG: basic skeleton 2023-08-01 09:20:57 -05:00

README.md

Formats Exposed

To develop, start a static file server in public/. There is no build step.

To deploy, copy the files from public/ to a static file host.

To run tests, run deno test.

To format code, run deno fmt.

To lint, run deno lint.

To run type checks, run deno task typecheck.

To run all checks (tests, linting, code formatting, and type checks), run deno task check-all.

Code style

  • Make sure all checks pass with deno task check-all.
  • Prefer arrow functions.
  • throw should be used when the developer makes a mistake, not for "expected" errors. For example, if someone uploads a bogus file, that shouldn't throw an error.
  • Bad news first:
    • If a function returns null if an error case, define the type null | Result, not Result | type.
    • Test error cases first.