luarocks / luarocks/luarocks-site
Warnings about name collision of modules
Nobody has claimed this yet.
- Dominant language
- MoonScript
- Stars
- 201
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
I think it would be convinient to be able check if this module name already used in some library.
E.g. LuaSocket library uses not only `socket` module name but also `mime` and `ltn12`.
But some libraries may use same base module name (e.g. `LuaCov` and `LuaCov-coveralls`) libraryes use same namespace `luacov`.
So I think `luarocks upload` and web UI should get warning if some one try create new library that contein modules with such names.
@hishamhm ping.
Contributor guide
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 by reviewing the `luarocks upload` flow and the web UI for creating libraries, since the issue names both entry points. Determine how module names are collected and compared, then consider the work complete when both surfaces warn about module-name collisions before a library is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- cli, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100