Fix resources filename mismatch when a dependency has a + #6151
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.
Resolves #6099
Short description π
The
ResourcesProjectMapper
would have a mismatch between referencing the bundle accessor file and the actual filename when the dependency had a +. To fix this, we no longer runcamelized
for the generated filename (I don't see why we'd need to do that).How to test the changes locally π§
Integrating
FirebaseAppMessaging-Beta
viaTuist/Package.swift
should work.Contributor checklist β
mise run lint:fix
Reviewer checklist β
changelog:added
,changelog:fixed
, orchangelog:changed
, and the title is usable as a changelog entry