bagelbotdev / api Goto Github PK

Route: /cart-resolver/:cartGuid.

This page should provide the cartGuid as metadata and show a page directing the user to install bagelbotdev/cart-resolver.

If installed, the extension will watch for this page and redirect the user to toasttab. Otherwise, they will simply see the page prompting them to install the extension.

Route: /v1/*

The bagelbot api should expose non-sensitive analytic data from the database over a public, REST-based api.

The following routes are proposed:

/v1/users: return all registered users: (fist name, last name, and their slack ids)
/v1/tabs: return all previous tabs where the opener mongo oid is swapped with the first_name and last_name joined with a space.
/v1/coin: return all users along with their current bryxcoin balances.

Currently:

Users will run /order <keywords>, and their order will be immediately added to the open tab.

Desired:

Users will run /order <keywords>, be prompted to confirm that what was pulled was correct, and then by clicking a "confirm" button, their order will be added to the open tab.

Currently:

Calls to the bagelbot.menuitems collection is cached. However, if the menu were to be updated without the deployment being restarted, the actual new items would not be updated.

Desired:

Someone with an admin slack user id will run /bbadmin clear-cache menu, which would clear the cache of the method that grabs the menu items from the database.

Currently:

To add a new menuitem to the database, you must either use the build-menu script, or manually connect with monosh.

Desired:

an endpoint, such as /db/insert/menuitem, would accept a token of the format <username>:<password encoded in base64. These tokens would be user specific, and they would have to contact a DB admin to get a token created for them. The endpoint would also take the menuitem spec and insert it into the database.

This would mostly be used by the menubuilder project for automatic menuitem insertion.

Some people are not morning people, but still love bagels. Since the order time is usually 45+ min, it would be nice to place the order the day before and select a time to have the order ready the next day.

Attempts to run yarn rollout appears to work fine, but when the newly built image is ran, the container runtime throws an error about an invalid exec.

General online research has found that this issue is common among users of M1/M2 chipsets.

If you aren't paying attention a tab can be opened and closed before you look at Slack. Bagel Bot should tag @channel or @here so we don't miss a tab!