shayanhabibi / shayanhabibi/Partas.GitNet
Projects with the same suffix prevent packing and pushing
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In a situation with two packages named similarly:
- Partas.Solid.ZagJs
- Glutinum.ZagJs
The name difference derives from the fact that Glutinum.ZagJs is supposed to be agnostic of Partas.Solid
The default scoping scheme assesses both as ZagJs.
While I could use the scoping function to match for this case and change it, it would be a boon if this occured by default. Perhaps an initial prefix for the scope based on the preceding chunk of the project file name?
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
No files, tests, or entry points are named. Start by locating the default scoping logic used during packing and pushing, then review how project file names are parsed. Done means similarly suffixed projects receive distinct default scopes without requiring a custom scoping function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100