Module naming conventions should allow underscore
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 136
- Forks
- 555
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 4
Description
In devdocs Module naming convention it is stated that:
- Module names should contain only lower case and numbers.
- Native modules' names must be prefixed with “ps_” (e.g. ps_linklist).
I suggest that the convention instead should be something like:
- Module names should contain only lower case letter, numbers and underscore.
- Developers are encouraged to prefix their modules with their own unique prefix, just like prestashop native modules are prefixed with
ps_. This makes it easier to avoid conflicts in module name collisions , allowing the merchant to both have (example) modulespsdevone_imageslideras well aspsdevtwo_imagesliderandps_imageslider. - Native modules' names must be prefixed with “ps_” (e.g. ps_linklist).
Why allow underscores?
- Because not allowing them means developers needs to change the name for hundreds of modules. Myself I have over 100 modules prefixed with "ko_" and most of them also has more underscores like "ko_product_homepage_slider"
- Because snake-case-names looks better and are
much_easier_to_readthannotusingunderscoresatall, in file-lists, databases and where ever.
Also discussed on slack
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.
Research direction
Start with the devdocs Module naming convention page and compare it with the linked Native modules guidance. Update the convention to cover lowercase letters, numbers, underscores, and developer-specific prefixes while retaining the ps_ requirement for native modules; done means the documentation clearly reflects these rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100