Kmaschta

For this issue, I get sometimes weird positions from the GitHub API. I opened a [thread on the GitHub Platform forum](https://platform.github.community/t/pull-request-review-comment-wrong-position-from-the-diff/7568).

I read that but I'm not convinced. The point of Sedy is to prevent the original requester to switch context and take care of the review. Moreover, the reviewer already...

Enable Sedy configuration with a `.sedy.yml` file can be a very nice feature, I agree!

I'm clearly for the usage of env variables :+1:

I've rebased the branch, if you want to take a look @brikou

:+1: The crappy mix between 1859's queries and TP's models is my fault. This separation would help us to separate the DB layer to model layer, as recommended in Domain-Driven...

Until we code a solution for the Image and Upload fields, here is a workaround: https://github.com/marmelab/ng-admin/issues/541#issuecomment-118265671

Hi, You are right, the `totalItems` "provider" is defined [in the routing](https://github.com/marmelab/ng-admin/blob/f35c2cede1d9219b8aade65440bf25218df1d4e9/src/javascripts/ng-admin/Crud/routing.js#L101). I don't know if it is related to the wepack build, but it seems that the `response` argument...

Tough one. Are you able to write a unit/E2E test or a script with a lot of fixtures to try to reproduce this error?

@jpetitcolas explained why we can't address this issue, in the PR #1067 > These changes may have some drawbacks. Indeed, some API may expect all the entity fields in the...