Skip to content
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

LWC compiler should warn/error when handler is missing - or better runtime error msg #325

Closed
midzelis opened this issue May 22, 2018 · 1 comment
Labels
developer productivity issues marked as such are intended to help developers to not trip down enhancement

Comments

@midzelis
Copy link
Contributor

Description

When handler doesn't exist, LWC should produce warning or error. Happens often if you refactor or because of typos.

Steps to Reproduce

https://playground.sfdc.es/projects/ByYXVjbk7/2/edit

<template>
    <input onchange={handler}></input>
</template>

Expected Results

Compiler error message, or better runtime error.

Actual Results

Poor runtime error only.

Browsers Affected

Version

  • LWC: x.x.x

Possible Solution

Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.

@caridy caridy added the developer productivity issues marked as such are intended to help developers to not trip down label Jul 5, 2018
@caridy
Copy link
Collaborator

caridy commented Nov 23, 2018

We now have a better error, but can't be a compile error due to inheritance, so, it is a runtime error.

@caridy caridy closed this as completed Nov 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer productivity issues marked as such are intended to help developers to not trip down enhancement
Projects
None yet
Development

No branches or pull requests

3 participants