The plugin doesn't recognize the steps written in F#

[chirkin-ef]

Hi all. I've faced up with the strange behavior of the plugin after the installation in Rider (2020.3.1-2020.3.3).
My solution contains the SpecFlow C# project with the .feature and .feature.cs files and F# project with the steps descriptions. F# project is a project reference for the SpecFlow C# project.
After the installation, the plugin underscores the scenarios in the feature file and notifies that there're no binded steps for these scenarios.
If I try to ignore this notification and just run the tests (both of the scenarios and Unit Tests window) - everything is OK. Tests are passing correctly.
Summarizing the facts, there're two suspicious moments here - I use F# for the steps description, and these F# steps files are placed in the different project. Could it somehow affect the plugin's work? Why does it underscore the scenarios?

[Socolin]

Hello,

The plugin is currently written to detect steps in C# files. We should be able to adapt this for F#, it just need some works and see what code can be reuse for F# and what is specific.

[suttorres]

I'm subscribing to this bug since it is something that is affecting my team. As mentioned above, tests run with no issues but it is very inconvenient not to being able to navigate to the steps code in F#. This is not an issue in Visual Studio, but we are leaning towards Rider as an IDE.
A quick sample to see this issue is in the SpecFlow samples: https://github.com/SpecFlowOSS/SpecFlow-Examples/tree/master/BowlingKata/BowlingKata-Fsharp

[Chief5385]

I'm having the same issue