Skip to content

Conversation

maciejpiotrowski89
Copy link

What

Adds infoplists parameter to documentation for ios_unit_test and ios_ui_test rules. Links to problem described in Issue #2776

Copy link

google-cla bot commented Aug 29, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@brentleyjones
Copy link
Collaborator

You'll also need to sign the CLA.

Comment on lines 166 to 182
# Add bundle attributes to make them visible in documentation
rule_attrs.infoplist_attrs(),
{
"bundle_name": attr.string(
mandatory = False,
doc = """
The desired name of the bundle (without the extension). If this attribute is not set, then the name
of the target will be used instead.
""",
),
"frameworks": attr.label_list(
providers = [[AppleBundleInfo]],
doc = """
A list of framework targets that this target depends on.
""",
),
},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This causes the test runner to be invalidated when these values change. I don't like that. Longer term it might be best to separate the test runner from the bundle (#2744 (comment)).

Short term, we could adjust apple/ios.doc.bzl and the like to point to the macro in apple/ios.bzl and add a hand-crafted docstring.

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