-
Notifications
You must be signed in to change notification settings - Fork 83
Emit warnings when conflicts detected in Info.plist key values #369
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
base: main
Are you sure you want to change the base?
Conversation
@swift-ci test |
It looks like one of the existing tests might have exposed an issue here:
|
Thanks, it seems like diagnostics was expecting only error messages, but my implementation is adding warning messages about type conflicts in addition to the existing error messages. This is fixed now. |
@swift-ci test |
@swift-ci test macOS |
@swift-ci test linux |
When a building setting is set from an info.plist key, if the same key is set from another source. The previous one will be silently overwritten. This pull request added detectConflict() to detects if two PropertyListItem values are in conflict and emits an appropriate warning message if they are.
Note
#5 and #364 was accidentally closed, after a bot used to automatically sync fork matches my fork to main. This pr re-introduce those changes along with a test case.
Resolves #5