Conversation
chaoneww
marked this pull request as draft
September 12, 2026 09:30
chaoneww
marked this pull request as ready for review
September 12, 2026 09:30
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
1 participant
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.
Description
Fix the template name in the AEM Content Fragment Editor code generation guide.
The instruction currently mentions
@adobe/aem-cf-admin-ui-ext-tpl, but the CLI output below shows@adobe/aem-cf-editor-ui-ext-tpl.Related Issue
#163
Motivation and Context
I noticed this while following the guide to create an App Builder project.
At the template selection step, the instruction and the CLI output showed different package names, so it wasn't clear which one to choose.
After creating the project, I confirmed that
@adobe/aem-cf-editor-ui-ext-tplis the correct template for the Content Fragment Editor.