ae03d69645
We now have enough output properties implementation working to change our API gateway examples and API wrapper to correctly wire the API routes to the ARNs of lambdas passed in to them. We both wire up the lambda to the route, but also create a permission specific to each route to assign to the corresponding lambda - providing least privelege needed for the API definition. Also adds `string#toUpperCase` and fixes NewUniqueHex to match how we are using it. |
||
|---|---|---|
| .. | ||
| aws | ||
| lumi | ||
| lumijs | ||
| lumirt | ||
| mantle | ||
| README.md | ||
lumi/lib
This directory contains some libraries that Lumi programs may depend upon.
Overview
The Lumi standard library underneath lumi/ is special in that every program will ultimately use it directly or
indirectly to create resources.
Similarly, lumijs/ is the LumiJS compiler's runtime library, and so most LumiJS programs will on it.
Note that these are written in the Lumi subsets of the languages and therefore cannot perform I/O, etc.
Installation and Usage
Eventually these packages will be published like any other NPM package. For now, they are consumed only in a development capacity, and so there are some manual steps required to prepare a developer workspace.
For each library <lib> you wish to use, please see its install.sh script in its root directory. This performs
installation so that it can be used simply by adding a dependency to it.
We currently use NPM/Yarn symlinks to ease the developer workspace flow. As such, you will need to run:
yarn link <lib>
In a project that intends to consume <lib> before actually using it. For example, yarn link @lumi/lumi.