generated from bazel-contrib/rules-template
-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typecheck-only rule #88
Labels
Comments
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Aug 29, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Aug 29, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Aug 29, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Aug 29, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Aug 29, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Aug 29, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Sep 5, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Sep 5, 2024
jbedard
added a commit
to jbedard/rules_ts
that referenced
this issue
Sep 5, 2024
jbedard
added a commit
that referenced
this issue
Sep 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
So far we told users they have to use
tsc_test
if they just want a rule that errors when.d.ts
inputs have typing errors. That's because Bazel won't run actions whose outputs aren't needed, and there are no outputs of ats_project(srcs=["foo.d.ts"])
where we just want the typechecker to run.But Bazel 6 has validation actions, as observed here #85 (comment)
so then we could have a typecheck-only rule, maybe it would be
ts_project
with some different behavior.The text was updated successfully, but these errors were encountered: