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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Configure if scheme should be created or not based on patterns #3013

Closed
thiagohmcruz opened this issue Apr 15, 2024 · 1 comment · Fixed by #3027
Closed

Feature Request: Configure if scheme should be created or not based on patterns #3013

thiagohmcruz opened this issue Apr 15, 2024 · 1 comment · Fixed by #3027
Assignees
@thiagohmcruz
Labels
feature request New feature or request
Milestone
Desired but not p...

Comments

@thiagohmcruz
Copy link
Contributor

The use case I have in mind is one wanting source files to be indexed when there's no intent to directly build the respective targets in Xcode.

The existing features related to scheme generation are very flexible but what I'm missing here is the ability to configure things in bulk based on patterns instead of having to list all involved targets explicitly.
@thiagohmcruz thiagohmcruz added the feature request New feature or request label Apr 15, 2024
@thiagohmcruz
Copy link
Contributor Author

thiagohmcruz commented Apr 15, 2024 •
edited

Maybe this is a new scheme_autogeneration_mode that pairs with another attribute specifying the patterns (or pass in a struct to scheme_autogeneration_mode)?

@thiagohmcruz thiagohmcruz self-assigned this May 14, 2024
@thiagohmcruz thiagohmcruz mentioned this issue May 14, 2024
Merged
brentleyjones added a commit that referenced this issue May 29, 2024
@thiagohmcruz @brentleyjones
Add xcschemes.autogeneration_config (#3027)
00bf884 
Resolves #3013 

The proposal is to introduce a `xcschemes.autogeneration_config` macro
to allow consumers to configure scheme auto-generation. I'm addressing
my particular use case of wanting to exclude certain schemes based on
patterns in their names but I'm open to discuss other
configurations/exclusion patterns folks might want to add here.

In order to test this note how running (from `examples/integration`)
`bazel run //:xcodeproj-incremental-bazel-sim_arm64` generates a project
that **does not** contain the undesired schemes `UndesiredScheme_Swift`
and `UnwantedScheme_Swift` even though the respective targets do exist.

---------

Signed-off-by: Thiago Cruz <thiago@squareup.com>
Co-authored-by: Brentley Jones <github@brentleyjones.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thiagohmcruz thiagohmcruz

Labels
feature request New feature or request
Projects
None yet
Milestone
Desired but not prioritized
Development

Successfully merging a pull request may close this issue.

Add xcschemes.autogeneration_config MobileNativeFoundation/rules_xcodeproj
2 participants
@brentleyjones @thiagohmcruz