-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Qute - deprecate Results.Result enum and introduce Results.NotFound #18110
Conversation
Note that this PR is a breaking change:
|
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building cf45d4f
Full information is available in the Build summary check run. Test Failures⚙️ JVM Tests - JDK 11 #📦 independent-projects/tools/devtools-testing✖ ⚙️ JVM Tests - JDK 11 Windows #📦 independent-projects/tools/devtools-testing✖ ⚙️ JVM Tests - JDK 16 #📦 independent-projects/tools/devtools-testing✖ ⚙️ Maven Tests - JDK 11 #📦 integration-tests/maven✖ ⚙️ Maven Tests - JDK 11 Windows #📦 integration-tests/maven✖ |
- in order to improve the error message when a property/method is not found - also use the quarkus.qute.property-not-found-strategy=throw-exception by default in the development mode - related to quarkusio#16076
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Great job!
found
by default in the development mode