Atlas App Services
37 results found
-
Support TypeScript
I know this is probably a very complex feature, but I'd like to work with TypeScript when writing functions.
Some stretch goals:
- full integration with VSCode so we no longer have to use the web editor
- add support for testing functions (through CI/CD)115 votes -
Upgrade Node.js version (from v10 to v14/v16)
It would be great if you can upgrade the version of Node.js used in Realm Functions (currently in version 10.18.1). Version 10.x, which was an LTS, has been unmaintained for many years. The end of life of Node v12 is scheduled for April 2022.
Is it possible to upgrade Node to version 14 (at least)? Another feature would be to let us choose the Node.js runtime version directly from Realm UI or the CLI (it's possible for example with AWS Lambda).
Working with Node v10 is really difficult for us since most of the dependencies are not compatible with it.
…
70 votes -
Increase of Functions timeout
Timeout is set to 90 seconds. This value is a fixed setting and is too low for extensive ingestion functions.
A default value of 600 seconds would be helpful.
Even better would be the ability to set an individual timeout value per application in the settings.
48 votes -
Folders for Functions, Values
Add folders to the Functions and Values areas and then to make it 10x better by adding permissioning by folder so we can keep our clients from altering sensitive functions/values in specific folders.
38 votes -
python
Python support would be great to allow us to have a single code base
32 votes -
Use node modules in Functions
As far as I understand currently it is not possible to use node/npm modules is Functions. Would be great to have it.
18 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 -
Support for arrayFilters in Functions
Can we add arrayFilters and other array update capabilities that already exist in MQL? Its is difficult to update arrays, and very easy to update an array in MQL in node.js for example.
12 votes -
function sandbox
It would be great to have a function sandbox area, where you can write and called previously used functions (saved like notepad++ does) without having to create the function and commit it.
This would be for trying thing out or performing quick tasks for which you don't want to go through all the hassle of formally creating a function.
8 votes -
Ability to set Values in Functions
Ability from webhooks and functions to call context.values.set() and set a value that can then be referenced somewhere later. This could dramatically cut back on calls to outside APIs as we need data in multiple places so we end up having to make several calls.
5 votes -
Postman snippet generator
Working with the http library has been the most frustrating part of working with Realm functions. Postman has an awesome "generate code snippet" feature, with lots of options like Axios and Unirest. It would great if I didn't have to manually convert from cURL and could just copy some code from Postman into my Realm function.
4 votes -
Autocomplete references for Functions, value and environment variables
It would be tremendously helpful if while referencing a function or a value or an environment variable - the IDE will autocomplete the possible options, for better efficiency and mistakes reduction. Going back and forth around the UI or trying to remember by heart is error prone, and copy-pasting is valid only for a single action at a time.
3 votes -
Flag to deploy individual functions
Run into many issues where devs deploy over one another. I understand that building the functionality to test realm functions locally could take a while to set up. However, deploying individual functions using a -f flag in the push scripts would be an alternative solution!
3 votes -
Expose dbstats / stats in Functions
Add to the allowable MongoDB actions to be able query the database size, like: db.runCommand({ dbStats: 1, scale: 1 }) or by collection like db.sources.stats()
3 votes -
Global Variables for Functions
Add global variables to Functions (so I don't have to pass around supposedly global variables to every function call).
Add support for typescript :)))
3 votes -
Meaningful errors
Descriptive errors are crucial for debugging and simply cannot be found with Atlas App Services !
1) If an error occurs - the whole function cascade is terminated - not only the steps following the error but also the ones prior to it. i.e. if a console.log was applied on a function that should have produced information before the error - that too will disappear and will not be displayed.
2) That is why it can take hours to find the exact location of the error this way, by trial and error.
3) If I was clever enough to console.error…2 votes -
display all functions currently using a value
While viewing a VALUE, it would be most helpful if there could be a list of all functions currently using it.
2 votes -
Support for appService functions
Being able to program the functions from vscode.
2 votes -
realm function limits should be configurable
realm function limits should be configurable or increased, as it hinders capabilities for memory heavy tasks like encryption/decoding
eg sha256 encryption using crypto can only perform upto 10000 iterarations while industry standards expects atleast a lakh iterations2 votes -
Bracket Pair Colorizer
It would be awesome if there could be an implementation of something like VSCode's Bracket Pair Colorizer.
It may spend a lot of time and attention to pair the start and ending of functions without a visual aid.
Thank you very much for the consideration.2 votes
- Don't see your idea?