Manuel

@Bhavyajain21 this may be interesting for you

Per user I'd say. I'm not sure how users are managed internally in Parse Dashboard, I think @dblythy could give advice on that, he worked on a few user features...

The auto-sort sorts the rest of the fields alphabetically, not randomly, that's what it's supposed to do anyway. Did you check whether `columnPreference` already supports predefined column sorting? It may...

Added bounty due to urgency for this change. cc @dplewis > In alignment with our [SDKs and Tools Maintenance Policy](https://docs.aws.amazon.com/sdkref/latest/guide/maint-policy.html), [AWS SDK for JavaScript v2](https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/welcome.html) will enter maintenance mode on...

See https://github.com/parse-community/parse-server-s3-adapter/pull/220

cc @parse-community/server This is a critical issue that will require everyone to upgrade the push adapter for continued FCM support.

@jimnor0xF That's amazing, thanks for taking a lead on this.

Basically for the review of the existing PR we just need to make sure it's not a breaking change for people who are for example using the current API that...

We'd need someone to test the PR out with their current set-up for node-gcm, so we know whether the push adapter still works without forcing to switch to the new...

@jimnor0xF I meant that when using the current configuration of the deprecated API, the adapter should work without any changes necessary in the config or code. In other words, when...