-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Compile Fails When Called Method Has Deep Destructed inputs. #2232
Comments
Are you using wasm? |
@kdy1, I am not using WASM but using typescript however looks like you were able to find and resolve the issue. Thanks. |
I think I closed it after testing your input, not fixing bug. |
Wonder if it makes any difference that the method that was having this issue was on an object similar to below....
|
@hkd987 The input you provided is wrong, because there's no body. |
And I verified that swc works well with your input |
I did not provide the method body for brevity sake so that we could focus on the issue at hand only. |
Something around this is blocking compile, I just cant put my finger on the exact issue. This is when using https://www.npmjs.com/package/@swc/jest |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Describe the bug
When calling a method that has multiple object inputs as separate inputs. SWC fails to compile when the objects are deconstructed deeply. To give context this is a graphql resolver that is being called.
Input code
When changing the called method below the code compiles
Error Message
Config
Expected behavior
Expect that when calling a method with multiple object inputs deep object destructing will work.
Version
The version of @swc/core: ^1.2.85
The text was updated successfully, but these errors were encountered: