@W-20609628 Folder Name Validation#466
Merged
sf-aastha-paruthi merged 2 commits intosalesforcecli:release260omnistudiopackagefrom Jan 16, 2026
Merged
Conversation
shaurabh-tiwari-git
approved these changes
Jan 16, 2026
shaurabh-tiwari-git
left a comment
There was a problem hiding this comment.
Test with folderName /classes as well for apex before merging. Other changes look good.
Collaborator
Author
d1dd087
into
salesforcecli:release260omnistudiopackage
1 check passed
This file contains hidden or 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
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?
If folder name contains reserved names like lwc, lables, others the deployment fails.
Added validation to check the name and inform the user.
What issues does this PR fix or reference?