[TASK] Use the standard names for the example extensions - #893
Merged
Merged
Conversation
The examples used several made-up names for the same things: site_package for the site package, some_extension and blog_example for an extension, and tx_my_table for its table. blog_example is discontinued, so readers can no longer look it up either. They now use the names the other manuals use: my_sitepackage for the site package, my_extension (myvendor/my-extension) for an extension, and tx_myextension_mytable for a table of that extension. The tables configured in the site package's page.tsconfig keep an extension prefix, as they belong to another extension, like tx_news_domain_model_news next to them. "composer require vendor\sitepackagename" becomes "composer require myvendor/my-sitepackage", the backslash was never valid in a Composer package name. Releases: main, 14.3, 13.4 Assisted-by: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Lina Wolf
|
Successfully created backport PR for |
|
Successfully created backport PR for |
sarahmccarthy123
pushed a commit
that referenced
this pull request
Sep 30, 2026
The examples used several made-up names for the same things: site_package for the site package, some_extension and blog_example for an extension, and tx_my_table for its table. blog_example is discontinued, so readers can no longer look it up either. They now use the names the other manuals use: my_sitepackage for the site package, my_extension (myvendor/my-extension) for an extension, and tx_myextension_mytable for a table of that extension. The tables configured in the site package's page.tsconfig keep an extension prefix, as they belong to another extension, like tx_news_domain_model_news next to them. "composer require vendor\sitepackagename" becomes "composer require myvendor/my-sitepackage", the backslash was never valid in a Composer package name. Releases: main, 14.3, 13.4 Assisted-by: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Lina Wolf Signed-off-by: Lina Wolf (cherry picked from commit 452fffc) Signed-off-by: Lina Wolf Co-authored-by: Lina Wolf <48202465+linawolf@users.noreply.github.com>
sarahmccarthy123
pushed a commit
that referenced
this pull request
Sep 30, 2026
The examples used several made-up names for the same things: site_package for the site package, some_extension and blog_example for an extension, and tx_my_table for its table. blog_example is discontinued, so readers can no longer look it up either. They now use the names the other manuals use: my_sitepackage for the site package, my_extension (myvendor/my-extension) for an extension, and tx_myextension_mytable for a table of that extension. The tables configured in the site package's page.tsconfig keep an extension prefix, as they belong to another extension, like tx_news_domain_model_news next to them. "composer require vendor\sitepackagename" becomes "composer require myvendor/my-sitepackage", the backslash was never valid in a Composer package name. Releases: main, 14.3, 13.4 Assisted-by: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Lina Wolf Signed-off-by: Lina Wolf (cherry picked from commit 452fffc) Signed-off-by: Lina Wolf Co-authored-by: Lina Wolf <48202465+linawolf@users.noreply.github.com>
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.
The examples used several made-up names for the same things: site_package
for the site package, some_extension and blog_example for an extension,
and tx_my_table for its table. blog_example is discontinued, so readers can
no longer look it up either.
They now use the names the other manuals use: my_sitepackage for the site
package, my_extension (myvendor/my-extension) for an extension, and
tx_myextension_mytable for a table of that extension. The tables configured
in the site package's page.tsconfig keep an extension prefix, as they
belong to another extension, like tx_news_domain_model_news next to them.
"composer require vendor\sitepackagename" becomes
"composer require myvendor/my-sitepackage", the backslash was never valid
in a Composer package name.
Releases: main, 14.3, 13.4
Assisted-by: Claude Opus 5.5 noreply@anthropic.com
Signed-off-by: Lina Wolf