Skip to content
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

feat: allow definition of alternative typescript repositories #675

Merged
merged 3 commits into from
Aug 23, 2024

Conversation

alexeagle
Copy link
Member

Hard-coding the npm_typescript repo was a design smell, and prevented users from having multiple.


Changes are visible to end-users: yes

  • Searched for relevant documentation and updated as needed: yes
  • Breaking change (forces users to change their own code or config): no
  • Suggested release notes appear below: no

Test plan

  • New test cases added

Hard-coding the npm_typescript repo was a design smell, and prevented users from having multiple.
Copy link

aspect-workflows bot commented Aug 23, 2024

Test

1 test target passed

Targets
//docs:update_2_test [k8-fastbuild] 29ms

Total test execution time was 29ms. 84 tests (98.8%) were fully cached saving 6s.


Buildifier      Format

Copy link
Member

@gregmagolan gregmagolan left a comment

Choose a reason for hiding this comment

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

🌮

@alexeagle alexeagle merged commit 3cfbd4a into main Aug 23, 2024
23 checks passed
@alexeagle alexeagle deleted the multi_ts branch August 23, 2024 20:30
gzm0 added a commit to gzm0/rules_ts that referenced this pull request Sep 13, 2024
This is a follow-up to aspect-build#675 which made the `@npm_typescript`
repository less special.

This replaces the (hopefully) last occurrence of this special name
that cannot be changed by configuration.

Alternatives I considered:

- Expose the `is_typescript_5_or_greater` flag on the `ts_project`
  macro:
  Simplest option at first, but since it is only used for config
  validation, that would become nonsensical.
- Add a `npm_typescript_package` or `npm_typescript_repository`
  parameter that would allow overriding all places where
  `@npm_typescript//` is used by default:
  Would offer more functionality (e.g. worker config checking), but
  would also be more invasive.
jbedard pushed a commit that referenced this pull request Sep 17, 2024
This is a follow-up to #675 which made the `@npm_typescript`
repository less special.

This replaces the (hopefully) last occurrence of this special name
that cannot be changed by configuration.

Alternatives I considered:

- Expose the `is_typescript_5_or_greater` flag on the `ts_project`
  macro:
  Simplest option at first, but since it is only used for config
  validation, that would become nonsensical.
- Add a `npm_typescript_package` or `npm_typescript_repository`
  parameter that would allow overriding all places where
  `@npm_typescript//` is used by default:
  Would offer more functionality (e.g. worker config checking), but
  would also be more invasive.
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.

3 participants