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

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

Closed
michael-hawker opened this issue Oct 10, 2017 · 0 comments
Closed

Comments

@michael-hawker
Copy link

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.

ztlevi pushed a commit to ztlevi/vue that referenced this issue Feb 14, 2018
f2009 pushed a commit to f2009/vue that referenced this issue Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant