-
Notifications
You must be signed in to change notification settings - Fork 1
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
Websmith addon testing api #43
Merged
Merged
Conversation
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
+ Support for virtual mode (everything in memory, no FS needed) + Add addons to the compilation from existing directory or from source string + Add project code to the compilation from existing directory or from source string + Remove need for fusion-fs in addon tests
…sults: + Add getCompiledFiles: returns all files in outDir + Add getCompiledFile: returns first matching file in outDir + Add getCompiledDir: returns absolute path to outDir + Add CompilationResults: with full access to the ts.EmitResult providing: * hasEmitSkipped: () => boolean; * getEmittedFiles: () => string[]; * hasFailures: () => boolean; * getFailureReport: (filter?: string) => string; * getDiagnostics: () => ts.Diagnostic[];
+ Not all emitted files are added to ts.EmitResult + tsLibDefaults cannot be added to file system, when browserSystem is used
…compilation environment
Note: It'll be replaced with @quatico/webbloqs-testing
…ed with addProjectFile API
… missing addons names
This is a major change in the AddonRegistry's lifecycle. No files are loaded upfront, no addons are compiled and activated in its constructor. + Don't read files initially, start with empty file system + Don't compile addons initially
+ Move AddonRegistry into the compiler as class property and provide a separate config parameter + Extend compile-system to configure and provide AddonRegistry separately + Remove addons from CompilerArguments
+ Add importDir as sourceFolder for addons to compile
…nto a separate directory in the buildDir
jwloka
force-pushed
the
websmith-addon-testing-api
branch
from
May 7, 2024 13:33
61c46f9
to
4d7da05
Compare
maur-o
reviewed
May 8, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR proposes an initial APII for simplifying compiler testing significantly. Setup the typescript compiler, customize projects settings, add custom compiler addons, and compile various projects within 5 lines of code. Use Unit Test style setup and assertions with Jest. Compile projects from the filesystem or from virtual file content and compare compiled results expected from the filesystem, or virtual snapshots.
The library can run tests, with
See README.md for more details