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
I wrote my first production FAKE script with FAKE 5 this week. I have to admit that getting there was quite a bit frustrating at times. For example if you get all red squigglies in VS Code suddenly because of IEquatable missing and you need to look for a solution in the issue tracker. This could easily be included in the getting started.
On top of that while the docs are generally good, I often needed to look at the source code (which is linked to, which is great!).
The primary reason for this post is this: The new FAKE 5 modularization docs desperately need a to include the NuGet a module's functions are available in. I found myself hunting the right package more than once using a separate browser tab querying nuget.org for e.g. fake nunit.
If that information is already included it is not prominent enough to find it.
The text was updated successfully, but these errors were encountered:
I wrote my first production FAKE script with FAKE 5 this week. I have to admit that getting there was quite a bit frustrating at times. For example if you get all red squigglies in VS Code suddenly because of IEquatable missing and you need to look for a solution in the issue tracker. This could easily be included in the getting started.
On top of that while the docs are generally good, I often needed to look at the source code (which is linked to, which is great!).
The primary reason for this post is this: The new FAKE 5 modularization docs desperately need a to include the NuGet a module's functions are available in. I found myself hunting the right package more than once using a separate browser tab querying nuget.org for e.g.
fake nunit
.If that information is already included it is not prominent enough to find it.
The text was updated successfully, but these errors were encountered: