Skip to content

Ability to explicitly specify output files in apple_core_data_model rule #2727

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

Conversation

daltonclaybrook
Copy link
Contributor

This PR contains one of the two fixes mentioned in #2726. This change makes it possible to explicitly specify the output files that are expected to be generated from the provided core data models. This causes the rule to return a provider containing these individual Swift files rather than just the containing folder.

@daltonclaybrook
Copy link
Contributor Author

@luispadron any thoughts on this latest change?

@luispadron
Copy link
Contributor

Looks good thanks for updating! Ill leave this here for another day or two to see if any other maintainers have thoughts then we can merge it

@luispadron luispadron merged commit c07c93e into bazelbuild:master Jun 9, 2025
8 checks passed
@daltonclaybrook daltonclaybrook deleted the dalton/core_data_explicit_outputs branch July 3, 2025 14:40
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.

2 participants