Add C# scripting support for .csx scripts#4
Merged
Merged
Conversation
The CSX tests require the dotnet-script global tool to execute .csx files via `dotnet script`. Without it, all CSX tests fail with "command or file was not found" on the CI runner.
MelbourneDeveloper
force-pushed
the
c#
branch
from
3f5f601 to
ad9312d
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR;
Details
Runner.fsto execute.csxscripts viadotnet script, addedCsxscript type toTypes.fs, updatedParser.fsto recognize.csxfiles.csxlanguage configuration and file associations inpackage.json, added C# script constants, integrated.csxexecution into the extension's playlist runneropenApiGenerator.tsfor generating API requests from OpenAPI specsCsxScriptTests.fs(F# core tests) andcsx-scripts.e2e.test.ts(VS Code e2e tests covering success, failure, compile errors, slow scripts, multi-output, and mixed F#/C# scenarios), plus playlist e2e testssetup.csx,teardown.csx,report.csx,smoke-tests.csx,validate-env.csx), acrud-csharp.naplistplaylist, and its HTML reportcsharp-scripting.mddoc page, updated all comparison pages, homepage, blog post, and README to reflect C# supportHow do the tests prove the change works
CsxScriptTests.fsverifies core.csxscript execution: successful runs capture stdout, failed scripts return error results, and compile errors are reported correctlycsx-scripts.e2e.test.tsruns full VS Code e2e tests against actual.csxscripts in playlists — validates output capture, error handling, compile error reporting, slow script behavior, multi-line output, and mixed F#/C# script playlistsplaylist.e2e.test.tstests playlist execution through the VS Code UICliIntegrationTests.fsextended with C# script integration tests for the CLI runner