fsprojects / fsprojects/FSharpLint
Tool name is `dotnet-fsharplint` while documentation states `fsharplint`
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 327
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
The project definition has <AssemblyName>dotnet-fsharplint</AssemblyName>, which means that the command is dotnet-fsharplint by default.
I think that we should use <ToolCommandName>fsharplint</ToolCommandName> (or set the assembly name) to align with the documentation.
I don't see any reason to prepend the command with dotnet-prefix.
@knocte @webwarrior-ws @Numpsy @Thorium do you have any thoughts?
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 locating the project definition containing dotnet-fsharplint and compare it with the documentation's command name. Decide whether fsharplint or an assembly-name change is appropriate, then verify that the packaged command matches the documented name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100