You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe the problem.
Since we have rolled out #22120, all (well, most) user-generated proxies now have nullabilities correctly reflect their backend counterparts. However in abp's built-in modules, some types still have incorrect nullability. E.g. EntityDto<TKey> in the @abp/ng.core package:
exportdeclareclassEntityDto<TKey=string>{id?: TKey;// should not be nullableconstructor(initialValues?: Partial<EntityDto<TKey>>);}
Describe the solution you'd like
Update these types with correct nullability.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Since we have rolled out #22120, all (well, most) user-generated proxies now have nullabilities correctly reflect their backend counterparts. However in abp's built-in modules, some types still have incorrect nullability. E.g.
EntityDto<TKey>
in the @abp/ng.core package:Describe the solution you'd like
Update these types with correct nullability.
Additional context
No response
The text was updated successfully, but these errors were encountered: