Guillaume
My feedback
12 results found
-
131 votes
An error occurred while saving the comment Guillaume supported this idea ·
-
83 votes
An error occurred while saving the comment Guillaume commented
@Dev agree with you, but when you say "this was not available" someone can think that it's now available in their API. Unfortunately, not at this moment. The only solution is still to create a custom resolver and use an aggregation to pagination data.
An error occurred while saving the comment Guillaume commented
ETA for this feature? We are in 2022 and it is difficult to understand why, such an important and critical feature, is not yet available.
Guillaume supported this idea ·
-
94 votes
An error occurred while saving the comment Guillaume commented
OP created this message more than two years ago. Since then we don't have any news from MongoDB. It is not in their roadmap. To be honest I'm not sure we'll see this feature in 2023...
Therefore on our projects, we are migrating all of our Realm Functions to Azure Functions. It's much better: TypeScript support, local development server, efficient CLI, etc.
Guillaume supported this idea ·
-
2 votes
An error occurred while saving the comment Guillaume commented
Hello,
It's also important for us. But instead of passing the user as a parameter, it would be better I guess to have access to the current signed-in user that has executed the request linked to the trigger. We need that to automatically update properties like `createdBy` and `updatedBy`.
Currently, we use parameter on the frontend side. It's not safe since the user can intercept the request and change the parameter.
Guillaume supported this idea ·
-
46 votes
An error occurred while saving the comment Guillaume commented
6 months later, no improvements. In the meantime, Node 18 has just been released.
Guillaume shared this idea ·
-
10 votes
Guillaume shared this idea ·
-
5 votes
Guillaume supported this idea ·
-
5 votes
Guillaume supported this idea ·
-
23 votes
Guillaume supported this idea ·
-
38 votes
Guillaume supported this idea ·
-
152 votes
Looking for feedback around this feature, please reach out to sumedha.mehta@mongodb.com if you have any.
Guillaume supported this idea ·
-
34 votes
Guillaume supported this idea ·
This is also crucial for us, especially for the development of lambda functions. That's why we have moved part of our Realm app logic to Azure (API, Azure Functions, etc.). We had a call with one of the MongoDB architects and product owners, and they advised us also to move to another provider for everything else than Atlas (database and Sync engine are great!).
MongoDB, do you have an ETA for this feature? What is the priority?