I'm not following why this is required.
Is there a problem with the ...WithUserDto or is this additional coding expected behavior?
I feel I would be better off creating a ..WithNavigationPropertiesDto to get the details of the Create/Modify/Delete user details. Do you have any sample code for using the ..WithUserDto?
My use case is to display the Create/Modify audit details in the UI - I was hoping the ..WithUserDto would provide this directly.
Sure.
I created a new entity using ABP Suite. The entity is simple with just two properties and is a FullAuditedAggregateRoot.
Then I manually changed the ABP Suite generated code in ...Application.Contracts BookDto.cs Line 6 in place of line 7. That is the only changed made.
The error occurs when changing the Entity Dto to FullAuditedEntityWithUserDto The BookDto no longer has an Id property
Toggling back line 7 to the original ABP Suite code, the error goes away.
ABP Framework version: v5.0.0-rc2 UI type: Blazor Server DB provider: EF Core Steps to reproduce the issue:"generate entity with required navigation property when there are nullable / not required properties on the entity" The build fails because "Optional parameters must appear after all required parameters" If the required navigation property is moved above the nullable items in the Domain entity definition the the build is successful.
ABP Framework version: v5.0.0-rc2 UI type: Blazor Server DB provider: EF Core
Frontend.Blazor.Page.Item.razor_cs.txt namespace %%solution-namespace%%.Blazor.Pages%%<if:IsModule>%%.%%only-project-name%%%%</if:IsModule>%%%%<if:IsMicroservice>%%.%%only-project-name%%%%</if:IsMicroservice>%%
This text is being included in the file when creating a Blazor Page: %%<if:IsModule>%%.%%only-project-name%%%%</if:IsModule>%%%%<if:IsMicroservice>%%.%%only-project-name%%%%</if:IsMicroservice>%%
Can I have an update on the progress for this issue.
My client is waiting for this issue to be resovled.
This issue is closed: https://github.com/abpframework/abp/issues/9589
I don't have acces to view this: https://github.com/volosoft/volo/issues/7206
Thank you
Perfect. thank you.
Thank you for your prompt reply. I have implemented this work around. Hopefully this is being worked on to be handled by the ABP suite.