Antoine Cormouls

Currently, case-insensitivity is only used for indexes/queries on email/username fields on User class. I can suggest: - preventCollation - disableCaseInsensitiveIndexAndQuery - preventCollationOnIndexAndQuery Collation is also the error name returned by...

Yes `enableCollation`, `transformEmailToLowerCase` and `transformUsernameToLowerCase` makes sense. Do you have a suggestion about "default injection" of `enableCollation` to `true`. Or i just use a `=== false` check in the code....

Real usage feedback: With this PR and options activated I currently succeed in running Parse Server in a fully Serverless env using Google Cloud Run (CPU only reserved during requests)...

HI @okobsamoht , i think you need to restore the package lock from alpha branch. Also you have changed the lockfile version to v2. To easily avoid a change to...

thanks @okobsamoht for the package lock restoration. Is it possible to add some screenshot of the new jsdoc theme here ? It could helps to understand the before and after...

Hi @brocklj could you provide the GraphQL request that you use in your migrations ? And how you inject your files into the graphQL request ? Feel free to provide...

Hi @brocklj I see that the fix is super simple. Could rebase this PR on alpha and add the failing test at the bottom of the ParseGraphQLServer.spec.js You have an...

Hi @brocklj Parse Server has switched to GraphQL Yoga with new graphql upload/file handling. Could you confirm that the issue is still present in Parse Server last alpha version? Also,...

This feature will also drastically improve GraphQL API. This PR is challenging and interesting to develop. I'll see one of my colleagues and I can dedicate a coding pair session...

Hi @ardatan, parse-server still use npm lockfile v1. So to install the project use `nvm use 14 && npm i` to avoid a lockfile migration. Then you should have less...