[Release Tooling] xcprivacy generation tooling (3) #12149
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Oh, build failures are because the ReleaseTooling package is being built with Xcode 14.1, but I used Swift syntax introduced in a version later than Xcode 14.1. Fixing... |
ncooke3
commented
Nov 29, 2023
paulb777
approved these changes
Nov 29, 2023
|
Moved rest of logic into this feature branch for future reference. Closing this PR. Will revert already merged PRs once I figure out if/what can be re-used in new approach. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the necessary model types that will live in the
PrivacyKitmodule. These types and their relation to one another is heavily based on the guidance at https://developer.apple.com/documentation/bundleresources/privacy_manifest_files.These model types are encodable so they can be encoded directly into a plist using Foundation's
PropertyListEncoder()PrivacyManifest.swiftis the "root" structure, so I'd recommend starting there.#no-changelog