Will Harney
Will Harney
Thanks for the clarification on the repro! > My assertion is that, In whichever cases we see an error "thrown" today, we would be seeing an "thrown" error even if...
Upon reflection, this change is not intrinsically observable, but the changed behavior can trivially be exposed. A component may bind `for:each` to an `@api`-decorated prop, which would delegate responsibility for...
What is the motivation for this change? Please also add some test cases to demonstrate the changed behavior.
When the LWC compiler encounters a babel error, it checks the message for the LWC decorators (`api`/`track`/`wire`), and provides a more helpful message if encountered (LWC1198, rather than LWC1007). However,...
@yashank676 please make sure the CLA is signed and add two test cases to `packages/@lwc/compiler/src/transformers/__tests__/transform-javascript.spec.ts`.
I think these test cases cover the different possible scenarios, but feel free to come up with your own. ```ts // Using an LWC decorator -- no comment import {...
Include whatever test cases you think are relevant, and have them assert the correct error for the regex used.
/nucleus test
It looks like you're having trouble with the GraphQL wire adapter, which is outside the scope of this repo (the LWC framework). For help with your issue, I would recommend...
This is an issue with a Lightning Component, not the LWC framework (this repo). To resolve your issue, I would recommend opening a [Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/tagged/lightning-web-components) question or a [Salesforce...