-
Notifications
You must be signed in to change notification settings - Fork 301
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Pass otherFSharpOptions to fable-standalone
- Loading branch information
1 parent
32f1090
commit 565bf9f
Showing
4 changed files
with
36 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
565bf9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alfonsogarciacaro This is actually not necessary, you can already pass otherOptions when you create the checker (see
IFableManager.CreateChecker
).It doesn't hurt either, but the options you added above are staying on the client side, they'll not be sent to FCS-Fable. The only way to set otherOptions right now is to create a new checker. We can change that, but the typecheck caching will have to change to account for options being changed on the fly, probably by flushing the cache (which is similar to making a new checker).
565bf9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I realized that when testing the REPL :/ Anyways, it's working now :) When activating "Preview F# features" you can open static classes but
nameof
is not working yet. I guess we need to create new metadata from latest FSharp.Core for that.565bf9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alfonsogarciacaro This is awesome, thanks a lot.
The export branch is rebased, if you want to run the
Export.Metadata
target for sdk 3.0 binaries (I promise to do it next time).565bf9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I tried running
Export.Metadata
and alsoGenerateMetadata
in the repl repository (after some rework), but the result is very strange. The new assemblies seem to work except for FSharp.Core, I cannot open the namespace and everything that's coming from there fails with "The value or constructor 'xxx' is not defined."However FSharp.Core.dll is correctly generated and I can see the browser is loading it 😕
565bf9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alfonsogarciacaro Yes, it is strange, supposedly the only difference in 4.7.0 is that it now references
netstandard2.0
.Let's stick with the previous version of
FSharp.Core
(4.6.2) (only for the REPL, of course) until we figure out what to do with 4.7.0.565bf9f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alfonsogarciacaro
Turns out
FSharp.Core
4.7.0 was missing some dependencies (added in #1916):System.Net.Requests
andSystem.Net.WebClient
.