You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 22, 2024. It is now read-only.
Note you can play around with deno lint --json and deno lint --compact to alter the output a bit.
I wanted to experiment with https://docs.deno.com/runtime/manual/tools/jupyter, so I started with --json and produced the following three cells. The integration seems a bit buggy, so the types are repeated in all three cells:
cell1:
This is actually pretty cool! Pretty interesting to use dax+jupyter for auditing the codebase, it reads like magic...
It might actually be very useful to have this script under tasks/... something like lint:audit/lint:inspect? Not sure if its possible/ergonomic to launch jupyter from a task... anyways, this should already help towards getting linting errors to 0
I've added an issue for getting the notebook into the codebase in some form. It might just be a file you have to work with, depending on whether it's possible to invoke it from the command line or not.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar to https://github.com/netzo/netzo/issues/88, but this time for
deno lint
. Currently we get:Note you can play around with
deno lint --json
anddeno lint --compact
to alter the output a bit.I wanted to experiment with https://docs.deno.com/runtime/manual/tools/jupyter, so I started with
--json
and produced the following three cells. The integration seems a bit buggy, so the types are repeated in all three cells:cell1:
output:
cell2:
output:
cell3:
output:
This offers a slightly more targeted approach to dealing with the 101 errors, which might make it more manageable.
The text was updated successfully, but these errors were encountered: