Skip to content

Conversation

devversion
Copy link
Contributor

@devversion devversion commented May 15, 2025

For Angular we fully rely on ts_project just with a custom tsc executable. We would like to have better distinction between Angular or TypeScript targets. It seems like it would be useful to control the progress message.

This would also allow better distinction when e.g. compiling with a different configuration. e.g. we use a transition for Angular to compile with a different compilation mode when shipping to npm.

Copy link

aspect-workflows bot commented May 15, 2025

Test

All tests were cache hits

173 tests (100.0%) were fully cached saving 12s.


Buildifier      Format

@devversion devversion marked this pull request as ready for review May 15, 2025 11:19
Copy link
Member

@alexeagle alexeagle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome! just needs a cd docs; bazel run update

For Angular we fully rely on `ts_project` just with a custom `tsc`
executable. We would like to have better distinction between Angular or
TypeScript targets.

It seems like it would be useful to control the progress message. This
would also allow better distinction when e.g. compiling with a different
configuration. e.g. we use a transition for Angular to compile with a
different compilation mode when shipping to npm
@devversion
Copy link
Contributor Author

@alexeagle ops, sorry. Pushed

@alexeagle
Copy link
Member

@devversion FWIW I've been experimenting with dropping the docs-checked-in pattern because it's always this last oops step for contributors, and no easy way to just "accept fix"

@alexeagle alexeagle merged commit 103b665 into aspect-build:main May 15, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants