Stitch

Inside Stitch, would be a great addition.

Please support the selection of a GitHub branch. Depending on the development process, you do not want to deploy the master branch.

The auto generated schema of an object containing an array of arrays isn't creating a GraphQL type and a warning is generated.

The current email/password authentication provider only really works for users that self-register. In the case where user access needs to be controlled, a user can be created via registerWithEmail(), but the new user needs to first confirm their email address and then trigger a second email that resets their password. This extra step is unusual and adds no security benefit to users. It would be most useful to allow a user profile to be flagged with a "password change required on login" attribute. An administrative user could setup the new user via registerWithEmail() which would trigger the email confirmation (as currently done). After the new user confirms their email address and logs in, the user would then be required to set a new password. This assumes the admin user communicates the temporary password to the new user, but this is a fairly common scenario across most systems today.

It would be useful to allow automatic deploy where the stitch app is in a subdirectory of the root of the git repository. One case is, where the Stitch app is one level down. The root directory has a build process that bundles multiple JS modules with rollup and writes the combined output to a stitch function in the subdirectory. Example: https://github.com/gmishkin/jeopardy The general use case is a monorepo where there may be multiple stitch apps deployed from a single repo, and they are located in the relevant part of the repo at some arbitrary level of nesting.

When using SSR framework like NextJS, in order to render protected data server side, you must establish a JWT or session on initial login. Subsequent requests will then grab user from session and get protected data. Google Firebase Auth lets you get their Auth token, pass it to server, and validate server side, allowing you to create a session via third party Auth service. Not sure how this would work with Stitch. Is it possible to render protected data on the server on initial load? If not, it would get rid of a lot of the benefits of SSR apps. Example of NextJS + Firebase auth: https://github.com/zeit/next.js/blob/master/examples/with-firebase-authentication/server.js

Just took GraphQL for a spin and it appears that it only supports exact matches on query parameters. If this is indeed the case, then what's the timeline for additional operators (lt, gt, in, nin, or, nested or/and)?

MongoDB Stitch React Native SDK is missing functionalities compared to other SDK for example "MongoDB Stitch Browser SDK" has the ability to watch documents in a collection for changes, such functionality is missing in the MongoDB Stitch React Native SDK.

I have been testing a basic app with a couple of clients and neither confirmed their email address after registering as the confirmation email came from no-reply+stitch@mongodb.com and was in no way related to the application as far as they knew. Obviously this isn't ideal. I think the ability to at least set a 'Sender Name' would be a lot better?

The confirmation email received from registerWithEmail is very primitive. The confirmation link didn't come across as a clickable link (at least not in Yahoo!). I know there's a separate request to edit the confirmation email body, but this should be easily doable while that feature is being developed.