[Blazor] Added one to many, many to many and enum support for blazor front

[nicolas63]

• Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green

• Tests are added where necessary

• Documentation is added/updated where necessary

• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

related to #165

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[ivanmonteiro]

Ok.
I have found that working with disconnected entities with EF Core tends to be tricky and unexpected errors can and most likely will happen.

Yes me too, do you want us to change that ?

For now we use what is already implemented.
Add a plan to change from detached-entities in the near future. To"attached" entities, where the framework does the change tracking. This (hopefully) should make development and customization of repository layer easier. The added cost is extra queries at save/update. As always, some consideration and feedback from other developers and community are welcome. @nicolas63 Should a new issue be created to discuss it?

If possible, create an application with entities and relationships set up, and manually creating new entities with the UI and set the relationships. Also update the records using the UI, by un-checking the dropbox/checkbox of the relationship. And check if the changes were properly persisted.

Yes, i have try with https://github.com/jhipster/jhipster-dotnetcore/blob/main/test-integration/samples/jdl-default/app.jdl who don't works today and now all operation is ok

I will push the blazor sample with relationships after the merge if you want try it

Go ahead and merge when you're ready

[nicolas63]

For now we use what is already implemented.
Add a plan to change from detached-entities in the near future. To"attached" entities, where the framework does the change tracking. This (hopefully) should make development and customization of repository layer easier. The added cost is extra queries at save/update. As always, some consideration and feedback from other developers and community are welcome. @nicolas63 Should a new issue be created to discuss it?

yes, i think work on #355 who can help us because we can work only with id rather than complete structure

[ivanmonteiro]

For now we use what is already implemented.
Add a plan to change from detached-entities in the near future. To"attached" entities, where the framework does the change tracking. This (hopefully) should make development and customization of repository layer easier. The added cost is extra queries at save/update. As always, some consideration and feedback from other developers and community are welcome. @nicolas63 Should a new issue be created to discuss it?

yes, i think work on #355 who can help us because we can work only with id rather than complete structure

Yes, you're right!