kcphysics / randomstore Goto Github PK

The backend and frontend are currently working on good faith, and are expecting data in specific formats, but doesn't check for it. One example of this is when the saveStore function is called in the front end. It either expects an error or the real data shape, but does not check for the real data shape.

Definition of Done

1. When all of the interaction points between the frontend and the backend have appropriate error handling

To make sure this lives a while, we should ensure we can make and test changes without effecting the user experience. To this end we should create a development environment instance of all items. This is what should be used during the development process, and when moving to prod, the appropriate pieces and parts are changed.

Definition of Done

1. A new DynamoDB table exists
2. A new Lambda exists
3. A new API Gateway exists
4. A new CloudFront Distribution exists
5. A new S3 bucket exists
6. 2 new CNAMEs and 1 new certificate for dev.randomstore.scselvy.com and api.dev.randomstore.scselvy.com

Right now, manual commands are executed to ensure that code is built appropriately. This ticket is focusing on one use case, development.

When in development mode, a Makefile or similar should exist that does the following:

1. Compiles the svelte app
2. Loads the svelte app to the appropriate s3 buckets
3. Invalidates the Cloudfront distribution
4. Compiles the go lambda
5. Uploads the go lambda to the correct position

Full CI/CD will be handled at a later time

Definition of Done

1. A documented way to execute the above

Allow users to edit the store name. This will allow them to set it to something that they would like that fits their campaign better.

Definition of Done

1. Given: A customer has generated a store

• When: The customer clicks the pencil icon next to the name
• Then: They can change the name and it persists everywhere

Currently, when a specific store is opened, there's no way to go back to the "home page" and generate your own store. This should be instrumented by making the logo at the top be a link back to the original page.

When clicked, this should "reset" the internal memory of the page so that its a blank slate.

Definition of Done

1. When a customer who loaded a specific store clicks on the top logo

• Then: They are navigated back to the orginal page

Right now, the app relies only on CORS to ensure that events are coming in from allowed sources. This should be changed and some level of authorization should be used. In this case, we should set and check a header value. While this isn't secret in any way, it ensures that the application sent it, or someone opened up chrome dev tools and figured it out.

Definition of Done

1. The API Gateway has an authorizer configured that will check a specific header field to ensure that it is correct
2. The Frontend will have the authorization scheme built into the front to make sure communications are correct
3. A Lambda authorizer (potentially in the same go file with a different entry point) exists such that it checks the header appropriately