-
Notifications
You must be signed in to change notification settings - Fork 483
PBXReferenceProxy: Add display_name attribute. #473
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
PBXReferenceProxy: Add display_name attribute. #473
Conversation
|
Can you confirm this fixes the issue? |
|
I actually have no idea how to test this when the gem source in on my machine, but if I open the class as I show in the bug, this issue is fixed. |
|
Works great. |
|
👍🏻 |
|
@barakwei thanks for doing this! Would you mind adding a unit test/spec and a CHANGELOG entry? |
|
I'd love to add tests, but just running |
|
@barakwei that's interesting. What command are you using to run the tests? |
|
Just |
|
Try running |
|
Yep that, and you can do |
This commit fixes a bug that when a reference proxy doesn't have a name, it's display name doesn't fall back to "ReferenceProxy" but to the path. This is manifested if you have a framework object in your project and it's referenced (usually by a build file) in a build phase.
6a14ac9 to
786215c
Compare
|
Done |
|
@barakwei thank you! |
This PR fixes a bug that when a reference proxy doesn't have a name, it's display name doesn't fall back to "ReferenceProxy" but to the path.
This is manifested if you have a framework object in your project and it's referenced (usually by a build file) in a build phase. In this case, the display name was "ReferenceProxy" and not "XXX.framework".
Fixes #472