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

Reenable FSharpLint in the product #799

Merged
merged 1 commit into from Jun 18, 2021

Conversation

baronfel
Copy link
Contributor

With FSharpLint updated to FCS 39, we can now reenable it here, along with the tests.

Should close ionide/ionide-vscode-fsharp#1533 when Ionide is updated.

Configuration = lintConfig
CancellationToken = Some ctok }
{ Ast = ast
Source = sourceCode.ToString()
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it might be nice to see if FSharpLint can move to an ISourceText-based interface to reduce the amount of memory required (as this will allocate a new string).

@baronfel
Copy link
Contributor Author

This is good to merge: the failures are in the (known flaky) rename test.

@baronfel baronfel merged commit e2acde0 into ionide:master Jun 18, 2021
@baronfel baronfel deleted the reenable-fsharplint branch June 18, 2021 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Linter not available
1 participant