-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Relationships to User are saved in a microservice architecture, but not rendered #19399
Comments
That's odd, I will take a look. |
@mraible this happens only with Neo4j? |
It works with 7.0.1 and Neo4J. I tried using PostgreSQL for both gateway and blog, but couldn't get it to work. |
@mshima I can confirm this particular issue is fixed by your PR! I confirmed with Vue and Angular. Feel free to close it, or leave it open for PostgreSQL. |
Closing since the bug is fixed. I'm planing a follow-up PR targeting v8. |
@mshima approved |
Overview of the issue
Today, I tried my original reactive microservices example from this blog post and everything works as expected. The example is created with v7.0.1 and you can save a
blog
entity with or without auser
and it all works.If you create this same example with 7.9.2, it saves the relationship to the user, but it does not render it on the list or view screens. Furthermore, Angular does not render the user's login on the list screen.
For more information, see #19342 (comment) and subsequent comments.
Motivation for or Use Case
This functionality existed in v7.0.1 and therefore should be supported in all 7.x releases.
Reproduce the error
Then, start all the Docker containers for the gateway and start it. Start Neo4j for the blog app and start it as well. Log in and navigate to adding a new blog. After you add a new one, you'll see it rendered on the list screen. However, if you navigate to the view or edit screens, the user's login is not displayed.
JHipster Version(s)
7.9.2
JHipster configuration
https://github.com/jhipster/jdl-samples/blob/main/reactive-ms.jdl
The text was updated successfully, but these errors were encountered: