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

Migrated to FSharp.TypeProviders.SDK NuGet package from referenced files #229

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

xperiandri
Copy link
Contributor

No description provided.

Copy link
Member

@sergey-tihon sergey-tihon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xperiandri I cannot merge it with failed CI, please take a look and explain your motivation for NuGet dependency on SDK.

nuget FSharp.SystemTextJson
nuget FSharp.TypeProviders.SDK >= 8
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. It is already a recommended way to use SDK? Dependencies always were a pain to TPs
  2. What is your motivation for this change?

@@ -194,11 +193,11 @@ type DefinitionCompiler(schema: OpenApiDocument, provideNullable) as this =
ty,
getterCode =
(function
| [ this ] -> Expr.FieldGetUnchecked(this, providedField)
| [ this ] -> Expr.FieldGet(this, providedField)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please explain this change as well.

Why we should not use Expr methods crafted for TP authors as part of TP SDK?
https://github.com/fsprojects/FSharp.TypeProviders.SDK/blob/master/src/ProvidedTypes.fsi#L536-L539

It is probably because you SDK out of assembly and have no longer assess to them... Hmm

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.

2 participants