Guillaume MOREL-BAILLY
My feedback
5 results found
-
160 votes
An error occurred while saving the comment Guillaume MOREL-BAILLY
supported this idea
·
-
115 votes
An error occurred while saving the comment Guillaume MOREL-BAILLY
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 MOREL-BAILLY
supported this idea
·
-
7 votes
An error occurred while saving the comment Guillaume MOREL-BAILLY
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 MOREL-BAILLY
supported this idea
·
-
70 votes
An error occurred while saving the comment Guillaume MOREL-BAILLY
commented
6 months later, no improvements. In the meantime, Node 18 has just been released.
Guillaume MOREL-BAILLY
shared this idea
·
-
40 votesGuillaume MOREL-BAILLY
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?