Manuel

I think [steps 4, 5](https://github.com/parse-community/parse-server/blob/master/CONTRIBUTING.md#parse-server-configuration) are missing

The changes only show some method renaming, this PR needs more info. As you know, we require an issue for a PR, to avoid these fundamental Q/As about PRs.

Easy test fix that needs to be done here...

So the dashboard is trying to sort by a field that doesn't exist, right? It's expected that Parse Server returns an error, but it should be a 4xx, not 5xx....

> removing the "order" flag in the class before deleting the field in case the class is being sorted by the target field. sounds good, but this is a Parse...

This is the Parse Server issue, so let's focus on the Parse Server side here and forget about the dashboard for now. The 500 http error comes from the server....

> errorMessage": ["code": 105, "error": "Invalid This should follow whatever naming convention is decided in https://github.com/parse-community/parse-server/issues/7444, so we get to some uniformity. If push errors are currently handled correctly by...

I think if we can come up with a policy that works, we can add experimental features to the codebase. It's just that the examples above show that an "experimental"...

I don't think anyone is doubting that. The point is that the challenges above are very real and need to be addressed before we add any experimental feature. Please feel...

If someone is solving this already in some way, I'd be interested how. Maybe there is a better way than the suggested solution above.