-
Notifications
You must be signed in to change notification settings - Fork 18
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
Steps in Linked feature files are showing up as undefined and Plugin Intellisense not working #23
Comments
Is there a workaround for this that anybody can suggest? |
Hello, I did not have time to check yet. It would help if you can provide us with a small project to reproduce the bug. |
Hi, Thanks for responding. I have added a project in my github for your reference... https://github.com/rdasan/LinkedFeatureFile/tree/master/LinkedFeatureFile The |
@Socolin Was that helpful? The sample project illustrating the issue? |
I'll check this tonight |
Can you verify if this build fix your problem ? https://github.com/SpecFlowOSS/SpecFlow.Rider/runs/2072240670 |
@Socolin Apologies for not getting back on this. I did not get a chance to check that build. But I have the latest Release installed now and it's still not working for Linked Files. |
@rdasan Is this working in Visual Studio for you? With SpecFlow 3.0 we dropped support for files that are at another location than under the project. The reason is, that there are some questions, we couldn't answer. Like where to generate the *.feature.cs file for linked files. |
@SabotageAndi I have not tried on Visual Studio. Right now in Rider, when I Link the |
Isn't it safe to generate the files to the same location as the original file? |
@nferrellcmg No, it is not. |
I am using my feature files as
.csproj
linked files. I need to to it in this fashion because my feature files are in a separate repo and I include them in the main repo asgit subrepo
. After that I just include the relevant.feature
file as a Linked file in my Test project. However when I do that, the SpecFlow Plugin intellisense like "Go To Reference / Find Usages" does not seem to work. Also the steps show up as undefined even though I have defined and implemented them. This problem does not cause a build or Test issue. I'm using the latest version of the Plugin,.net 5.0
andxUnit
testing frameworkThe text was updated successfully, but these errors were encountered: