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

HasErrorParameter / setParameter behavior change #3860

Closed
OlliTietavainenVaadin opened this issue Apr 11, 2018 · 0 comments
Closed

HasErrorParameter / setParameter behavior change #3860

OlliTietavainenVaadin opened this issue Apr 11, 2018 · 0 comments
Assignees
Labels
Milestone

Comments

@OlliTietavainenVaadin
Copy link
Member

Issue came up in training:

  • If a MyException inheriting RuntimeException is thrown in the setParameter method and there is an error view implementing a matching HasErrorParameter, 10.0.0beta1 and 10.0.0beta6 behave differently
  • beta1 shows the error view
  • beta6 shows
Reason: Failed to parse url parameter, exception: org.vaadin.olli.MyException

Available routes:
<root> (requires parameter)
This detailed message is only shown when running in development mode.

Not sure if this is an intended change or not, but I think I prefer the error view being shown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants