-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/sn 733 use calculated properties inside navigation #86
base: develop
Are you sure you want to change the base?
Feature/sn 733 use calculated properties inside navigation #86
Conversation
@@ -65,6 +65,12 @@ public void Configure(EntityOptionsBuilder<Shop> entityOptionsBuilder) | |||
.SetIsSortable(true) | |||
.SetSearchType(SearchType.ContainsCaseInsensitive); | |||
}) | |||
.IncludeProperty(address => address.FullAddress, builder => | |||
{ | |||
builder |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can it be sortable?
@@ -65,6 +65,12 @@ public void Configure(EntityOptionsBuilder<Shop> entityOptionsBuilder) | |||
.SetIsSortable(true) | |||
.SetSearchType(SearchType.ContainsCaseInsensitive); | |||
}) | |||
.IncludeProperty(address => address.FullAddress, builder => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if we can apply the same Fluent API for the calculated properties. Some of the builder methods are useless for them, like SetIsExcludedFromQuery
or smth. In the future, we can have even more.
SN-733
Changed logic of getting calculated properties metadata, now it similar to ordinary properties, so a user can configure it just the same as usual property. Also, they will be displayed by default and can be added as part of a navigation.