Skip to content
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

split up FSharp.Data take 2 #1462

Merged
merged 4 commits into from
Aug 17, 2022
Merged

split up FSharp.Data take 2 #1462

merged 4 commits into from
Aug 17, 2022

Conversation

dsyme
Copy link
Contributor

@dsyme dsyme commented Aug 17, 2022

Continues #1457 after #1459 caused revert #1460

Will require this workaround in the TypeProvider SDK fsprojects/FSharp.TypeProviders.SDK#388

@dsyme
Copy link
Contributor Author

dsyme commented Aug 17, 2022

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)

@dsyme
Copy link
Contributor Author

dsyme commented Aug 17, 2022

Changed the version number to 6.0.1-beta001

@dsyme dsyme merged commit fd0fbcc into fsprojects:main Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant