Mapping profiles

[alicicek1]

Is there any way to map all properties instead o line by line for all entities?

protected override SievePropertyMapper MapProperties(SievePropertyMapper mapper)
        {
            mapper.Property<SurveyUserEntity>(a => a.Survey.Type)
                .CanSort()
                .CanFilter();
            mapper.Property<SurveyUserEntity>(a => a.CreatedByUser.SchoolId)
                .CanSort()
                .CanFilter();

            return mapper;
        }
`

[hasanmanzak]

This would require to walk through object structure that would bring whole all lot of overhead. And way more edge case handling: what would happen with cyclic dependencies? That brings "CyclicDependencyHandler" or "...Policy" etc. Indecisive, I am..

[alicicek1]

Yes can be but can't sieve realize which model I have been filtering for? For ex, I have CreatedUser in my base entity related to the UserEntity and I send request to a service , those services methods take a Model as a parameter and should I map all entities for filtering for CreatedUser.Name?

[maskalek]

Also don't like this behaviour that you have to explicitly mark all properties you need. There should be a method "CanSortAll" or a default setting.