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
However, it does not override the default Prefix value, which remains as per the base class Prefix = typeof(TModel).Name;
This creates ambiguity on the field names, where it is easily possible to have multiple keys of the same name, if classes used on IEntity have the same property names.
e.g.
public record PropertyA(bool Allow);
public record PropertyB(bool Allow);
PropertyA and PropertyB will be stored seperately in the properties dictionary correctly, but the views will create a form post with identical names.
The text was updated successfully, but these errors were encountered:
Agreed. Specially if you want to inject multiple things into the shape like. I had to implement a wrong around for this on couple places already. Here is one
It may be also best to use both the TEntiry_TSecrion. Like if we are using site setting it should be ISite_SiteSettings. It is on my to do, but a PR from you would be nice.
Currently the
SectionDisplayDriver
usesTSection
for it'sEntity
property name :OrchardCore/src/OrchardCore/OrchardCore.DisplayManagement/Entities/SectionDisplayDriver.cs
Line 28 in ae2f952
However, it does not override the default
Prefix
value, which remains as per the base classPrefix = typeof(TModel).Name;
This creates ambiguity on the field names, where it is easily possible to have multiple keys of the same name, if classes used on
IEntity
have the same property names.e.g.
PropertyA
andPropertyB
will be stored seperately in the properties dictionary correctly, but the views will create a form post with identical names.The text was updated successfully, but these errors were encountered: