ES6 cleanup and use MongoDB as a backing store #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Similar to other SS cleanup projects: ES6 used and general tidyup. This also uses MongoDB as a backing store rather than a file system, which allows SuperScript to scale (on AWS Lambda etc).
Motivation and Context
Have a common ES6 basis across all SS projects for better readability and code quality in general, and allow SS to scale by having central fact database on a server, rather than distributed filesystem folders of facts (which would have to be sync'ed somehow).
How Has This Been Tested?
Run all existing unit tests with success.
Types of changes
Only breaking change is that
sfacts.expand()
is no longer exposed to the user. It was previously aliasingsfacts.create()
, so this should be used instead.Checklist: