[Nitro CLI] Add --exclude-by-tag option to compose command#9110
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds support for the --exclude-by-tag option to the fusion compose command, enabling users to exclude schema elements by tag during composition without needing to create an archive first and then use the settings command.
Changes:
- Added a new
ExcludeTagListOptionclass for handling the--exclude-by-tagcommand-line option - Modified
FusionComposeCommandto accept and process the exclude-by-tag option during composition - Added comprehensive test coverage with test resources demonstrating tag exclusion functionality
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| ExcludeTagListOption.cs | New option class defining the --exclude-by-tag command-line argument for accepting a list of tags to exclude |
| FusionComposeCommand.cs | Updated compose command to retrieve, pass through, and apply the exclude-by-tag option throughout all execution paths (standard, watch mode, and file watching) |
| FusionComposeCommandTests.cs | Added test case Compose_Valid_ExcludeTag to verify the exclude-by-tag functionality works correctly |
| source-schema-1.graphqls | Test resource containing a GraphQL schema with fields tagged with "exclude-1" and "exclude-2" |
| source-schema-1-settings.json | Configuration for the first test schema |
| source-schema-2.graphqls | Test resource containing a second GraphQL schema without tagged fields |
| source-schema-2-settings.json | Configuration for the second test schema |
| composite-schema.graphqls | Expected result showing that fields with "exclude-1" and "exclude-2" tags are excluded from composition |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
tobias-tengler
approved these changes
Feb 13, 2026
This was referenced May 13, 2026
Open
This was referenced May 21, 2026
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.
Previously
exclude-by-tagcould only set on the settings command, which can only be run after an archive file has already been created. This leads to a problem if all sources need to be merged without a specific tag. This change updates the nitro compose options to support excluding by tag.