-
Notifications
You must be signed in to change notification settings - Fork 6
Add Atlaspack V3 config and integration tests for new transformers #916
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
base: main
Are you sure you want to change the base?
Conversation
Add integration tests
🦋 Changeset detectedLatest commit: 171e77c The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Missing ChangesetNo changeset found in PR. |
Rust Package Changeset Check
Options:
Example: |
📊 Type Coverage ReportCoverage Comparison
Files with Most Type Issues (Top 15)
This report was generated by the Type Coverage GitHub Action |
📊 Benchmark Results📊 Benchmark ResultsOverall Performance
🔍 Detailed Phase AnalysisThree.js Real Repository (JS)
Three.js Real Repository (V3)
💾 Unified Memory AnalysisThree.js Real Repository (JS) Memory Statistics
Sample Counts: JS: 14, Native: 303 Three.js Real Repository (V3) Memory Statistics
Sample Counts: JS: 14, Native: 468 🖥️ Environment
|
marcins
left a comment
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.
Nice one!
| .get(&Atom::from("NATIVE_SSR_TYPEOF_REPLACEMENT")) | ||
| .is_some_and(|v| v == "true"); | ||
| let global_aliasing_config = match env_vars.get(&Atom::from("NATIVE_GLOBAL_ALIASING")) { | ||
| Some(value) => match serde_json::from_str::<HashMap<String, String>>(value) { |
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.
Do we want to cache this value so it's not parsed on every file?
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.
I think it's probably not worth the effort and extra maintenance given the efficiency of Serde and the miniscule scale of the configs
Motivation
My recent transformers lacked Atlaspack V3 config parsing or any integration tests (just unit tests), this little followup remedies that.
Changes
Checklist
docs/folder