feat: allow aggregate to output to specific file #22
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.

Add transitive dependency support to formatjs_aggregate
TL;DR
Added support for transitive message aggregation and improved documentation for cross-platform compatibility.
What changed?
outattribute toformatjs_aggregaterule to specify custom output file namestransitive_messagesexample that demonstrates proper traversal of the dependency graphHow to test?
Build the new transitive messages example:
Verify that messages from module1 are included even though it's only a transitive dependency:
bazel test //examples/aggregate/app:aggregation_testTest on different platforms to verify consistent output across macOS, Linux, and Windows
Why make this change?
This change ensures that the formatjs_aggregate rule properly handles transitive dependencies, which is crucial for large monorepos where message dependencies might be nested several levels deep. The improved documentation makes it clear that the rules work across all major platforms without special configuration, which helps users understand the cross-platform capabilities of the toolchain.