You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Correct me if I'm wrong, but I understand that keeping all code in a single file is meant to ease embedding BoDi as a source file in a consuming project.
As this hurt readability of PRs (I hit that for #24), did you consider publishing a source nuget to allow embedding BoDi as source code for people not wanting to rely on the binary form ?
Example of such source code package can be found here: https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Sources/
I'm not aware of any good reason to do this except to share code that is meant to be private a a repo while still needing to be share, which seems not the case here, but in case this would help to provide more readable contributions...
Regards,
The text was updated successfully, but these errors were encountered:
FYI this was suggested nearly 3 years ago as #9 and there's some commentary there about it. Perhaps it is high time to reconsider. AFAIK SpecFlow dotnet core support is completed and has been for quite a while.
Hello,
Correct me if I'm wrong, but I understand that keeping all code in a single file is meant to ease embedding BoDi as a source file in a consuming project.
As this hurt readability of PRs (I hit that for #24), did you consider publishing a source nuget to allow embedding BoDi as source code for people not wanting to rely on the binary form ?
Example of such source code package can be found here: https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Sources/
I'm not aware of any good reason to do this except to share code that is meant to be private a a repo while still needing to be share, which seems not the case here, but in case this would help to provide more readable contributions...
Regards,
The text was updated successfully, but these errors were encountered: