@W-20799435 feat: add WebApplication metadata type #1672
Conversation
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
Shinoni
changed the title
Shinoni
commented
Jan 15, 2026
| // lwc, aura, waveTemplate, experiencePropertyType, lightningTypeBundle, contentTypeBundle | ||
| if (type.strategies?.adapter === 'bundle') { | ||
| // lwc, aura, waveTemplate, experiencePropertyType, lightningTypeBundle, contentTypeBundle, webApplications | ||
| if (type.strategies?.adapter === 'bundle' || type.strategies?.adapter === 'webApplications') { |
Author
There was a problem hiding this comment.
Added a custom adapter because WebApplication has extra source‑time requirements beyond a normal bundle: it must include webapplication.json and at least one non‑metadata content file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Implemented the new top‑level WebApplication metadata type (folder webapplications, suffix webapplication) and wired it into SDR’s registry, adapter, and path generation, with strict source validation: deploy now requires metadata XML + webapplication.json + at least one non‑metadata content file (e.g., src/index.html). Retrieve remains aligned with standard metadata resolution behavior.
What issues does this PR fix or reference?
Support for the new MD type.
@https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00002SNx2RYAT/view@
Functionality Before
<insert gif and/or summary>
Functionality After
A developer will be able deploy and retrieve a web app via sf cli
<insert gif and/or summary>