Atlas App Services
257 results found
-
Retain GraphQL Query History
The GraphQL feature has a history list while you stay on the page. It would be a great improvement if it maintained that history even if you navigated away and came back.
2 votes -
Add line number to function call error messages
A simple line number of where a function fails would be incredibly useful. And a function name would be important too for when a function calls another function.
12 votes -
Adding or removing elements from array fields
It would be helpful to support array add/remove in update mutations. I've been running into this most often when dealing with one-to-many relationships.
For example, adding/removing books from an author. Currently, you would have to fetch the entire array of books to add or remove the book linked to the author. If I could supply the foreign key to add/remove from the relationship that would be fantastic.
36 votes -
View cloud data in Realm Studio mongodb
Realm Studio is helpful to explore data from Legacy Realm Cloud. But Realm Studio mongodb does not support opening 'Realm Cloud'.
Please consider this feature.
Thanks so much,3 votes -
views
Use views (not materialized) as source for realm sync (potentially as read only)
2 votes -
GitHub Deploy - pulling deletes standard files, like LICENSE, README.md, etc.
If I make a change in the UI, deploy, then do a git pull on my local machine, the pull deletes my License, README.md, and .gitignore files. These are standard files and should not be changed on pull. It's like it's overwriting everything from scratch instead of just doing a diff. My repo is public and I need to include this basic info.
1 vote -
nodemailer Support
Nodemailer is currently not supported because of the punycode dependency. Would be nice to send mails directly on the mongodb server.
5 votes -
Allow community submissions to documentation
Let's face it, the Realm documentation as a whole is really lacking in comparison to the level of documentation of Atlas and other enterprise-level products. There have even been times I've had to search the old stitch documentation to understand how something works, and many other times I'm left experimenting or abandon a feature completely (for example, I gave up on Environments).
Other places have had success putting documentation on GitHub and allowing community submissions via pull requests.
Please allow the same -- I would happily contribute rather than needing to maintain my own notes (for me and my team)…
2 votes -
on premise solution
Allow MongoDB to be used for on-premise solutions to offer early on integration or govcloud support for Realm.
34 votes -
logs
When filtering logs I should be able to enter a date/time in the near future for the To date in order to produce a shareable URL in the address bar that will include log lines in the range from some specified date in the past until "now" without having to precisely enter what "now" is.
2 votes -
More flexible Custom User Data / User Linking
On Stitch, you can have multiple providers for identity, but then it creates multiple users even with the same email address if you have someone from say Google or then someone who authenticated via email. There is a way to merge two accounts, but it requires the user to authenticate twice and that's not an ideal user experience. One solve is to treat them as one user. The other solve is to create a user metadata collection which both identities can reference, but if you're trying to add rules and permissions you can't put an array of options in the…
36 votes -
More Mongo DB actions parity with the Node driver
The actions available via https://docs.mongodb.com/realm/mongodb/actions/ do not match the API exposed by the Node driver.
For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#createindex function would be extremely useful for our use case, I can't see any method for programmatically creating indexes via Realm.
For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#bulkwrite function returns a completely different type from https://docs.mongodb.com/realm/mongodb/actions/collection.bulkWrite/, making unit testing our realm functions locally extremely difficult.
I'm unsure what reasons there are for this disparity (especially when I can use the mongo node driver to connect locally to an Atlas cluster, but I can't use any of these methods in our deployed application in Realm).
1 vote -
Dark Mode
Support a "Dark Mode" for the MongoDB Realm UI.
39 votes -
Retry function
We use Realm functions to update related documents in our Mongo Atlas cluster. Sometimes, the DB connection (via
context.services.get("mongodb-atlas")) fails. We should... be able to retry establishing a connection? (Or even easier, just configure a retry for the Realm Function itself.)2 votes -
Support parquetjs or parquetjs-lite dependencies
Our product would like to read the parquet file-format from an S3 source. Both parquetjs and parquetjs-lite are incompatible with Realm's dependency upload.
parquetjs: "boto" module is a duplicate of a top-level Realm default library.
https://www.npmjs.com/package/parquetjsparquetjs-lite: Parse error when uploading tarball. See screenshot below.
https://www.npmjs.com/package/parquetjs-liteThank you!
3 votes -
Passwordless authentication provider
Passwordless logins are quite commons nowadays. Firebase supports "Login with email link" (https://firebase.google.com/docs/auth/web/email-link-auth). Would be nice to have the same in Realm.
5 votes -
Custom Query Filters
While you can create custom resolvers for 3rd party data or functions, this doesnt help me use graphQL to search existing types. I want to be able to query an existing type based on a contains. I know that this is a complex issue, but if we could create a custom query filter like we do for in, gt, lt, etc, I think this would help make the graphQL API more usable.
Currently, we are reduced to either using the limited query abilities, or recreate everything from scratch.
For instance:
I have a query currently:
query {
authorizationGroup(query: { name:3 votes -
Automatically Refresh Auth Tokens on User's Custom Data Change
Currently, getting updates to custom user data on the frontend requires periodically refreshing the token. A potential improvement would be for MongoDB Realm/SDKs to detect these changes automatically and streamline the token refresh so application code wasn't required to handle this case.
34 votes -
Allow one-to-many relationships in Realm GraphQL
Two collections A & B. One field say _id of collection A is the "foreign key" for a field say "field1" in collection B.
A: {_id:1, k1:v1, k2:v2}
B: {f1:1, x1:y1} //Values of field f1 correspond to values of _id in A
B: {f1:1, x1:y2}For one value of _id in A, there can be multiple corresponding documents in B. If we create a relationship currently in Realm GraphQL, only one document is fetched. The expected result set is 2 documents.
The current cumbersome workaround is to add an array field in collection A with all corresponding document IDs from…
4 votes -
Search Users by Email
In the users tab, I can only search by ID. If I don't have the users ID, it's nearly impossible for me to find a user in the list. Need to be able to search for a user by email ASAP. Thanks.
12 votes
- Don't see your idea?