-
Notifications
You must be signed in to change notification settings - Fork 79
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
test: Add react mixed test module #6865
Conversation
Add a mixed React Hilla Flow test module to test interoperability of the 2 features Fixes #4972
Dependencies Report
|
08e058a
to
f322b92
Compare
vaadin-platform-react-hybrid-test/src/main/frontend/views/hilla/components.tsx
Show resolved
Hide resolved
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.
I couldn't find the following test cases:
- Navigation lifecycle events handling on server: that event is triggered with expected number of times
- Server-side API for browser navigation: History::back/forward, History::pushState/replaceState
Do you think this isn't needed?
/** | ||
* Utility function for importing style modules. This is a temporary | ||
* solution until there is a standard solution available | ||
* @see https://github.com/vaadin/vaadin-themable-mixin/issues/73 |
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.
This issues seems resolved, maybe this file is not needed?
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.
Probably can be removed. I just started with a full copy of the original hybrid module.
import com.vaadin.flow.router.RouterLink; | ||
|
||
@Route("flow") | ||
public class FlowMainView extends VerticalLayout { |
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.
I don't know why this doesn't happen in the validation of this PR, but locally I get
Caused by: com.vaadin.flow.server.InvalidRouteConfigurationException: Invalid route configuration. The following Hilla route(s) conflict with configured Flow routes: flow
because this view has apparently the same mapping as views/flow/@index.tsx
.
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.
Even if I remove views/flow/@index.tsx
, it still throws, because apparently it sees an entry with "flow" path in the file-routes.json
.
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.
I fixed it by using "flow-flow" mapping for Flow view.
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.
There was the check for duplicate routes PR just a while ago and this one is older than that.
But just removing the @index.tsx
from the flow folder should be enough. Probably the mapping check needs some change on this.
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.
Just removing it doesn't help. Perhaps we have a bug in conflicts detection in Flow.
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.
Ok, validation passes.
I'm not certain it is run as it is behind the profile. Same as the other hybrid which I don't know where it is executed.
@ZheSun88 any idea on the execution? |
At least yesterday I saw that these IT tests were running according to the log. |
pom.xml
Outdated
@@ -76,6 +76,7 @@ | |||
<module>vaadin-dev-bundle</module> | |||
<module>vaadin-prod-bundle/pom-unoptimized.xml</module> | |||
<module>vaadin-prod-bundle</module> | |||
<module>vaadin-platform-react-hybrid-test</module> |
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.
The test module is behind a profile and added in the standard list of modules, maybe we should excluded it from here and leave it only behind a profile?
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.
Yes.
@ZheSun88 could you please add this profile to CI when appropriate? |
Add a mixed React Hilla Flow
test module to test interoperability
of the 2 features
Fixes #4972