fix: pass org data when building ComponentSet with wildcard metadata #824
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
chore: refactor long fn out
|
QA: ✅ works fine, except for namespaces on Layouts which aren't caused or fixed by this PR.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
When retrieving metadata with wildcard matching (e.g.,
--metadata "ApexClass:Prefix_*") pass along the org connection data to query the org for matching fullNames of that type. This allows retrieving metadata with wildcard matching into an empty project, or a project that doesn't already contain all the matching metadata being retrieved.Also adds unit tests and NUTs for wildcard matching.
NOTE: also need the associated SDR PR: forcedotcom/source-deploy-retrieve#1182
What issues does this PR fix or reference?
@W-14284096@