JetBrains/resharper-fsharp

This system is the F# language support plugin for JetBrains Rider, providing a comprehensive IDE experience for F# development. It integrates with the F# Compiler Service to deliver features such as code completion, refactoring, debugging, and static analysis. The plugin also manages external tools like Fantomas for code formatting and F# Interactive for interactive scripting, ensuring a cohesive development environment.

This period focused on establishing the initial F# backend support for JetBrains Rider, involving a significant architectural overhaul that replaced legacy parsing and PSI infrastructure with a modern, modular plugin structure. Concurrently, the team extensively expanded the test suite to cover code completion, navigation, refactoring, and syntax highlighting, ensuring the new implementation was robust and complete.

71 changes

This period was dominated by the addition of extensive test data and unit tests for the F# language plugin. The work focused on validating code actions, quick fixes, and daemon analysis features, ensuring correct behavior for a wide range of F# syntax and semantics.

76 changes

This period focused on completing the F# plugin's feature set by implementing core IDE integrations such as code completion, refactoring, debugging, and static analysis. The work also involved significant architectural improvements, including the introduction of an out-of-process type provider host and a comprehensive test suite migration to JUnit 5.

108 changes

This period focused on deepening F# integration across the IDE, introducing new features such as sticky scrolling, AI-driven syntax checking, and enhanced debugging capabilities for async workflows. Significant effort was also dedicated to expanding test coverage for lexer, parser, and intention actions, alongside implementing specific behavioral changes like disabling context navigation for functional members.

28 changes

JetBrains/resharper-fsharp was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.