ECOMMERCE.md's six 'Commerce ...' module names generate stutter repositories
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- laravel
- Domain
- documentation
Research direction
Open projects/ecommerce/ECOMMERCE.md and review the catalogue tables in sections §3–§16, focusing on the six module names with a leading “Commerce”. Remove that redundant prefix from each name, then verify the catalogue uses the capability names consistently with the ecommerce-laravel naming convention.
Written by the indexing model from the issue text.
Description
projects/ecommerce/ECOMMERCE.md names six modules with a leading "Commerce" — Commerce Core, Commerce Customers, and four others — inside the Ecommerce product.
Because repository names are module-{product}-{capability}, those six generate stutter repositories:
module-ecommerce-commerce-core
module-ecommerce-commerce-customers
Six such repositories are already provisioned.
Why this is a naming problem and not a cosmetic one
The alternative to renaming is a collapse-the-repeated-word rule, and that rule has to be applied by hand by every author of every module in every product. A convention that requires a special case for six rows out of 105 is a convention that will be applied inconsistently.
ecommerce-laravel resolved it by treating ECOMMERCE.md's catalogue as authoritative and renaming the six stutter repositories, so commerce-core reads ecommerce-core throughout its plan.
Ask
Drop the redundant "Commerce" prefix from the six module names in the §3–§16 catalogue tables. The product word is already ecommerce; repeating it in the capability is what produces the stutter.
Found while auditing ecommerce-laravel against the standards.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from liberusoftware/documentation
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
MODULES.md section 9 puts a module- prefix in Composer package names that no published package uses Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
All issues in liberusoftware/documentation
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·