Repository navigation
feat: extract messages from runtime dependency graphs - #129
Merged
Merged
Conversation
longlho
marked this pull request as ready for review
November 6, 2026 13:00
longlho
enabled auto-merge (squash)
November 6, 2026 16:02
longlho
pushed a commit
that referenced
this pull request
Nov 6, 2026
🤖 I have created a release *beep* *boop* --- ## 0.13.0 (2026-11-06) ## What's Changed * chore(deps): update bazel-contrib/publish-to-bcr action to v1.6.0 by @renovate[bot] in #126 * feat: extract messages from runtime dependency graphs by @longlho in #129 **Full Changelog**: v0.12.5...v0.13.0 --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Consumers collecting messages from native dependency graphs currently duplicate extraction wiring around their language rules.
Add one configurable
formatjs_message_collector_aspect. Runtime labels resolve configured aliases; a provider predicate supports language-specific runtime detection without importing language rules. The public provider exposes onlycatalogsanduses_runtime.Private source plans preserve configured source identity and explicit coverage. Selected roots evaluate those plans once, filter eligible sources, and register extraction. Scope decisions follow source declarations through wrappers; allowing a generator in one configuration cannot enable its rejected output in another. Libraries keep plans in depsets, and excluded producers are not execution inputs.
Rule adapters select roots with
collect_at; CLI users pass--aspects_parameters=formatjs_root=//app:main. Extraction uses one batch per root, or per-file catalogs when source locations are requested. Consumers own merging, duplicate-ID policy and runtime installation. Existing explicit catalogs remain unchanged.The existing collection-only entrypoint and
formatjs_extractrule remain compatible. The new factory API has not shipped.