cps-org / cps-org/cps

Package name specification needs refinement

Open
#68 4 comments 0 reactions 0 assignees View on GitHub
enhancement scheduled
Dominant language
Python
Stars
191
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Right now, the specification says that "package [...] names may consist of ASCII letters, numbers, hyphens (-), and underscores (_), and may not contain forward-stroke (/) or at-sign (@)." This is both too restrictive and too liberal; we should probably also explicitly exclude all characters not allowed in FAT file names (`<`, `>`, `:`, `"`, `\`, `|`, `?`, `*`), and we should *add* `+` and `.` to the set of officially blessed characters, as these are used in existing package names. (As a bonus, this also makes the naming schema nearly identical to what CMake considers acceptable target names.)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names only the package-name specification, not a file or test. Start by locating that specification and reviewing the four comments; done means the allowed-character rules explicitly exclude the listed FAT filename characters and include + and . while matching the project’s agreed wording.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.