Test with Qute fluent API #872
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There appears to be a legitimate test failure |
angelozerr
force-pushed
the
qute-test-fluent-api
branch
from
b75853b to
20fb03f
Compare
Signed-off-by: azerr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test with Qute fluent API
I created this PR because in IJ the Qute fluent API (with template.data("key1", key1).data("key2", key2)...) didn't work, see redhat-developer/intellij-quarkus#876
We already support in JDT Qute fluent API but we have no tests, that's why I created this PR to have this kind of test and to have the same test than IJ.