Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MemberNames rule triggers on compiler generated delegate member #717

Open
joprice opened this issue Nov 5, 2024 · 0 comments
Open

MemberNames rule triggers on compiler generated delegate member #717

joprice opened this issue Nov 5, 2024 · 0 comments

Comments

@joprice
Copy link

joprice commented Nov 5, 2024

Description

When setting MemberNames to camelCase, the rule triggers on delegates, where the Invoke member is compiler-generated, and as far as I know, out of the users's control:

Consider changing `Invoke` to camelCase.
Error on line 127 starting at column 33
  type Target4<'a, 'b, 'c, 'd> = delegate of string * 'a * 'b * 'c * 'd -> unit
                                 ^
See https://fsprojects.github.io/FSharpLint/how-tos/rules/FL0045.html

Repro steps

Please provide the steps required to reproduce the problem

  1. Configure the memberNames.config.naming field to CamelCase
  2. Define a delegate and run linter

Expected behavior

Compiler generated members should not be candidates for lints where they are out of user control

Related information

  • Operating system - OSX
  • Branch - 0.24.2+143ae50e0e32d0842fa36c1bc22c735f2c72f114
  • .NET Runtime, CoreCLR or Mono Version - 8.0.303
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant