chore(ci): type check entire project in ci#1538
Conversation
317b46b to
cbb4b9c
Compare
|
Thoughts on removing the extra type checks? Thoughts on why we type check individual items in every matrix run? I picked This is fortunately passing now. |
|
Thanks, I think that's very similar to what I've done in #1454. So maybe I'll pull the changes to So here in this PR I'd have...
Any thoughts on my confusion around the existing type checks in CI? And how it runs for all matrix variations? |
cbb4b9c to
76a366f
Compare
iuioiua
left a comment
There was a problem hiding this comment.
LGTM! It's OK to run the type check on all platforms + versions.
Ok, I can remove the condition then. Should I also remove the other type checks, now that we're checking everything at once? |
|
Sure 🙂 |
Please rerun CI 🤞 |
marvinhagemeister
left a comment
There was a problem hiding this comment.
LGTM, thanks for adding this 👍
The logical continuation of #1536 and #1537. Now that the project is clean (after those are merged), we should prevent any such errors from sneaking in again in the future.
A question here: why are individual things type checked in the CI? Specifically:
Opening as a draft because:
I do agree that
deno check --remote init.tsshould remain separate, but the other four seem superfluous if we decide to check the whole project.