-
Notifications
You must be signed in to change notification settings - Fork 3.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
ValueObject not stored / useable #9835
Comments
Found a workaround for now ( Source Define navigation after OwnsOne for additional configuration
still prefer to use annotation for this configuration to DRY for every entity that use value objects ( so almost all ) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
push |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
ValueObjects seems to be not stored by default and [Owned] doesnt work when using ValueObjects with abp. ( Microsoft Source )
You can force ef to store them but it will ignore futher configuration ( like IsRequired ) and it requires you to always define the column name for ValueObjects with multiple properties
checked all examples but you dont use ValueObjects at all so im a bit curios if it works at all ?
Would be great to see an example about how to use ValueObjects and specific as primary ( to prevent using plain GUID and assign a GUID from a different entity )
ABP Framework version: 4.4
Database provider: EF Core
The text was updated successfully, but these errors were encountered: