fsprojects / fsprojects/FSharpLint

New linter is going crazy on perfectly fine elmish code

Open
#296 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
F#
Stars
327
Forks
74
PR merge metrics
No merged PRs in 30d

Description

Originally reported to ionide. Please see https://github.com/ionide/ionide-vscode-fsharp/issues/997

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Ionide issue 997, since this report provides no FSharpLint file, test, or reproduction details. Reproduce the linter diagnostics on the referenced valid elmish code, then identify the relevant lint rule and add coverage showing that valid code is no longer flagged.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.