collection.bulkWrite() in Mongodb stitch functions
I try to call collection.bulkWrite() in Mongodb stitch functions, but I get error - “bulkWrite is not a function” . Is it possible to use bulkWrite() in Mongodb stitch functions?
Syntax highlighting doesn't support async/await
Although Stitch functions support async/await, the syntax highlighting will show errors in the UI on the lines where async/await is used: 'Missing semicolon.'. This is very confusing for users.
Reduce Logs Lag.
Testing Functions using console.log() and the Function console is not always possible. Sometimes relying on Stitch Logs for debugging or troubleshooting is the easiest way to get to the root cause of the problem. The issue is that very frequently Stitch Logs are out of sync. More than 30 min behind the current operations (On an M0 cluster). This slows down the troubleshooting/development process significantly. Since Stitch requires Online Development. Making sure that the Log delay is minimal will greatly improve the Development experience.
Redirected to Atlas after inactivity
When not using Stitch for a certain amount of time (~15mins), the user is automatically redirected back to Atlas when trying to navigate anywhere within Stitch. This causes the user to have to navigate back to the app and back to screen where he/she was which is not an optimal user experience.
Triggers Unreliable After Disable
Disabling and re-enabling a trigger causes all triggers to no longer fire. Deleting the trigger and recreating it does not help. All triggers in the app stop working.
Triggers_Stitch App Region
The Triggers_Stitch App created when you first create an Atlas Trigger is always created in the us-east-1. It would be nice if there was an option to create it in the same region as the cluster to reduce latency/data transfer billing.
Provide count() method in Stitch db.collection.find()
Currently there is no way of determining the number of documents that were returned prior to actually consuming all the documents (by using .toArray() or iterating through .next()). It would be really helpful to provide a count() method that specifies the number of documents in the result.
Can we add arrayFilters and other array update capabilities that already exist in MQL? Its is difficult to update arrays in Stitch, and very easy to update an array in MQL in node.js for example. I fear this may slow adoption of stitch for development teams that are doing development with complex nested arrays.
Enable Function Testing (TDD/CI/CD)
It will be great if Tests could be defined within the Stitch UI. For example having the option to write a jest test that is executed before deploying any changes to the Hosted app would be awesome.