Replies: 1 comment
-
|
I would guess the reason is very similar to why it can't be used in routes: #729 I'll keep an eye on this changing in Blazor and as soon as it's possible, I'll update Vogen (I too would love to use Vogen in forms, routes, and parameters) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If we have an object with (say) a
stringproperty, then in a BlazorEditFormwe can do the following...However, if
nameis a value object, then this doesn't work, as (presumably) theInputTextcomponent assumes that the property being bound has a public getter and setter. As value objects don't have those, it looks like we can use them for any properties that we want to edit in a Blazor form.Is there any way around this? I know I can create a model for the form which uses the underlying primitive data type, but apart from adding yet another representation of the entity (on top of the database model and the DTO), it kind of removes the basic advantage of VOs in the first place.
Anyone able to help here? Thanks
Beta Was this translation helpful? Give feedback.
All reactions