W-16618249 fix: resolve fullname correctly for EmailTemplateFolder #679
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
WillieRuemmele
approved these changes
Sep 25, 2024
QA Notescreate an org with multiple layers of email templates / email template folders ✅ : |
iowillhoit
changed the title
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?
Some SourceMember types are mapped to different metadata types in SDR. EmailTemplateFolder is one of them; it maps to EmailFolder which is treated as an alias in SDR. The FullName parsing was updated to use the entire FullName rather than following a substring pattern for other mapped types like Aura and LWC.
What issues does this PR fix or reference?
@W-16618249@
forcedotcom/cli#2902