Fable Compatibility ✨

[Freymaurer]

I made FSharpAux Fable compatible!

• Using #if FABLE_COMPILER #else #endif ...-logic i removed all code incompatible with Fable, without touching on the dotnet part.
• I added more logic to the pack build task to create an addition FSharpAux.Fable package, which includes the raw FSharp source files.
• I set up a test environment with node.js test server using Fable.Mocha to recycle all relevant dotnet tests for fable testing.
• I added runtestsfable build task into main publishing pipeline

Todo:

• [x] Adjust gh-actions

[Freymaurer]

Example for mocha tests

[Freymaurer]

• Split codebase in core fsproj, which MUST be fable compatible and FSharpAux fsproj with all functions, which are fable incompatible.
• Split tests in the same way.
  • Core tests are still tested in both dotnet (expecto) and fable.mocha
  • All tests are discoverable by VS community test explorer (except native mocha tests of course)
• Added native mocha test example in tests/FSharpAux.Mocha.Tests.
  • /fable contains the fable transpiled tests and all fable transpiled source code in /fable/src
  • Main.js is currently used as default entrypoint from mocha by specifying this folder as entry.
  • fake buildtask runtestsfable, which executes npm test in root does the following in exactly this oder:
    • 1: transpile core and core.tests sourcecode with fable
    • 2: run transpiled core.tests in mocha
    • 3: run native mocha tests on transpiled sourcecode from 1

[Freymaurer]

@kMutagene @omaus @HLWeil ready to merge i think

[kMutagene]

I'll take a detailed look tomorrow, especially regarding the packing workflow, but looks great so far 👌

[Freymaurer]

I added a watchtests fake tast to run ALL tests in watch mode in parallel:

Example startup:

Any changes to the test repos are propagated to the relevant test suits and live updated in the console 🎉

[HLWeil]

Amazing stuff! Just two quick questions:

1. Shouldn't the Mocha Native Tests point to FSharpAux.Core?
2. Also in the CI workflows, you have a dotnet test and a fable test step, but the transpiled mocha tests get executed in both cases. What's the rationale behind this?

[Freymaurer]

@HLWeil

Shouldn't the Mocha Native Tests point to FSharpAux.Core?

Yes, you are right, i connected the wrong node.

Also in the CI workflows, you have a dotnet test and a fable test step, but the transpiled mocha tests get executed in both cases. What's the rationale behind this?

I don't see what you mean. Right now we have the following fake tasks:

Run

• runTestsJs: which runs Fable.Mnocha and Mocha native
• runTestsDotnet which runs Expecto dotnet tests
• runTests: which executes the both above

Watch

• watchTestsDotnet ~runTestsDotnet but in watchmode
• watchTestsJs: ~runTestsJs but in watchmode
• watchTests: runs both of the above in parallel

let me know if this clears this up