Closed dsyme closed 2 years ago
I've manually tested that updating to the latest TPSDK with the workaround makes the packages usable.
#i """nuget: C:\GitHub\dsyme\FSharp.Data\bin"""
#r "nuget: FSharp.Data, 5.0.3"
open FSharp.Data
type Auth = JsonProvider<"""{ "test": 1 }""">
let auth = Auth.Parse("""{ "test": 1 }""")
printfn $"{auth.Test}"
Then
fsi.exe a.fsx
and editing a.fsx
in Visual Studio.
It's not easy to automate this testing - our doc generation does consume the DLLs but not the packages we build. (Consuming built packages within the build itself is always surprisingly painful with .NET, as you have to use a local soure and make sure you're really getting the package version you built)
Changed the version number to 6.0.1-beta001
Continues #1457 after https://github.com/fsprojects/FSharp.Data/issues/1459 caused revert https://github.com/fsprojects/FSharp.Data/pull/1460
Will require this workaround in the TypeProvider SDK https://github.com/fsprojects/FSharp.TypeProviders.SDK/pull/388