WIP: Use all relative paths for header_mappings_dir option in podspecs
#39178
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.
Summary:
Possible follow-up for #39177
From what I understand from the
header_mappings_diris that it basically a relative path from the pods source root, and since all previous paths pointed to the root level of the pod's source roots I think having them all use./should result in all header structures being preserved.https://www.rubydoc.info/gems/cocoapods-core/0.38.2/Pod%2FSpecification%2FDSL:header_mappings_dir=
Changelog:
Test Plan: