-
Notifications
You must be signed in to change notification settings - Fork 2
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
React 18 #81
base: master
Are you sure you want to change the base?
React 18 #81
Conversation
+ Added interop for new filterNode option for prettyDom + Fixed misc. tests — JS CHANGELOGS — - https://github.com/testing-library/dom-testing-library/releases/tag/v8.0.0 - https://github.com/testing-library/react-testing-library/releases/tag/v12.0.0
"@babel/cli": "^7.12.13", | ||
"@babel/core": "^7.12.13", | ||
"@babel/plugin-transform-runtime": "^7.12.15", | ||
"@babel/preset-env": "^7.12.13", | ||
"@babel/preset-typescript": "^7.12.13", | ||
"babel-plugin-transform-inline-environment-variables": "^0.4.3", | ||
"@rollup/plugin-babel": "^5.2.3", | ||
"@rollup/plugin-commonjs": "^17.1.0", | ||
"@rollup/plugin-json": "^4.1.0", | ||
"@rollup/plugin-node-resolve": "^11.1.1", | ||
"rollup": "^2.38.5", | ||
"rollup-plugin-filesize": "^9.1.0", | ||
"rollup-plugin-node-builtins": "^2.1.2", | ||
"rollup-plugin-node-globals": "^1.4.0" | ||
"vite": "^5.4.9" |
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.
Wow that's cool that vite replaced all those!
@@ -58,7 +58,7 @@ void main() { | |||
var numRuns = 0; | |||
await rtl.waitFor(() async { | |||
numRuns++; | |||
expect(numRuns, 5); | |||
expect(numRuns, 3); |
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.
Is this just to make the test faster or did waitFor change somehow?
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.
Good question, we should look into this; will probably just have to try changing it locally and see what happens
external bool? Function(Node?)? get filterNode; | ||
external set filterNode(bool? Function(Node?)? 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.
Is there a reason the arg and return value aren't typed as non-nullable like in the TS type?
external bool? Function(Node?)? get filterNode; | |
external set filterNode(bool? Function(Node?)? value); | |
external bool Function(Node)? get filterNode; | |
external set filterNode(bool Function(Node)? 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.
Good catch; not that I'm aware of, and we can probably update this
@sydneyjodon-wk Thanks for the comments! You cool if we address those in the follow-up to add dual-17/18 support? |
@greglittlefield-wf yep that works for me! |
i love this |
@kealjones-wk you mean the parts that you did? 😁 |
No description provided.