feat:data shaping

[DavidPavlovski]

Implemented data shaping trough query params.
The fields parameter is optional. If left empty we will get all of the properties of the requested resource.

Example:

/api/Users/e3171502-622c-4a05-beb8-0c4c37f48401
The response will be:

{
   "id": "e3171502-622c-4a05-beb8-0c4c37f48401"
   "userName": "exampleUser",
   "email": "email@example.com"
}

but if we add the fields parameter:
/api/Users/e3171502-622c-4a05-beb8-0c4c37f48401?fields=userName

The response will only contain the requested properties

{
   "userName": "exampleUser"
}

Also we can separate field names with comma to select multiple properties:

/api/Users/e3171502-622c-4a05-beb8-0c4c37f48401?fields=id,userName

The response will only contain the requested properties

{
   "id": "e3171502-622c-4a05-beb8-0c4c37f48401",
   "userName": "exampleUser"
}

closes #197

[fvanderflier]

Not sure if I follow the logic behind having almost identical lines of code in both extensions? Can't we just re-use the generic or object extension here with using smth like source.Select(o => o.ShapeObject)?

[DavidPavlovski]

We can do that, but the main reason behind why its written like this initially is optimization purposes. In the IEnumerable extension the propertyInfo list is cached since it is an expensive operation and doing it for every single element in the list would be very performance heavy. It can be changed, but this is the main reason why its made this way.

[DavidPavlovski]

This issue has been resolved. Now instead of using extension methods, we have a DataShaper service, and we are caching the propertyInfos inside a dictionary field. And we only have one implementation of the data shaping logic instead of the two as we had before

[fvanderflier]

just a suggestion: I would call this something like DataShaper for example. First of all because it doesn't really extend object but it is a generic.

[fvanderflier]

Like the idea overall. Would suggest some unit tests to find some hidden and nasty edge-cases if they exist.

[DavidPavlovski]

Like the idea overall. Would suggest some unit tests to find some hidden and nasty edge-cases if they exist.

Unit tests are implemented, we have a lot of coverage for this part. We will see if any bugs arise in the future.