Skip to content

checkExpression should include the e.message in the error output #6771

@michael-hawker

Description

@michael-hawker

Version

2.4.4

Reproduction link

https://jsfiddle.net/gLqharts/

Steps to reproduce

  1. Open up browser console
  2. Run
  3. Inspect output warning message, says expression is invalid, but not why it's invalid.

I had to dig all the way to checkExpression in order to see the actual parsing exception to give me a clue. It should add the 'e.message' from the catch to the warning output.

(Also, VS will eat the end of the message if the template is long, so maybe put the template after the error message?)

What is expected?

More descriptive error messaging to help resolve an issue.

What is actually happening?

Only pointing out where there is a problem, but not what the problem is.


In this case, the message isn't as helpful, as I didn't realize at first I had to put single-quotes around this particular class name. You have the example in your docs that I missed, it could be good to call out this extra bit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions