Acceptance Criteria

1. Not getting things from test canvas
2. Hook up so we pull down user's list of canvases

Acceptance Criteria:

• The website no longer writes to the test ref in firebase, but writes to user-specific grids

BLOCKED: #23

Acceptance Criteria

1. Four placeholder pages based on the structure we determine
   1.1. Reorganize components into folders accordingly
2. If possible, start layout component wrapper route

Acceptance Criteria

1. Canvas previews on home page should link to correct canvas page when clicked
   1.1 Partly a bug, because the react router link is hardcoded in atm

Unit tests should be written for the backend service

Blocked by #56 until required actions/reducers are written.

Acceptance Criteria

1. Display all canvases user is member of on their home page
   1.1 Keep the static image for now, once we have the screenshot API in place, we can retrieve the capture from Firebase

Acceptance Criteria

1. Be able to add image to canvas

Acceptance Criteria

1. Define set of allowed user actions based on user type
2. Document rules
3. Send to team for approval before implementing

Acceptance Criteria

1. Images get cut off when resized, fix this

Acceptance Criteria

1. Set up redux so
   1.1. Drag and drop values are passed through redux
   1.2. Directory structure reorganized accordingly

Complete db schema (with current information).
Populate with some mock data

Acceptance Criteria

1. Have a demo-ready prototype, including
   1.1. Basic functioning signup/login
   1.2. Create canvas
   1.3. Basic click & drag on canvas
   1.4. User can access previously saved canvases

Create all actions and reducers based on what front-end team gives. This includes writing all unit tests and integration tests (and fixing the pre-existing ones)

We want to get previews of each canvas to display on the homepage.

Ian says some things might be formatted wrong so find em
/**?

Acceptance Criteria

1. Transformations shouldn't apply to all elements on canvas

Acceptance Criteria

1. Create service to handle user sharing, admin functions, etc.
   Note: not final functionality

Acceptance Criteria

1. Change the structure of the state for redux
2. Fix tests so that they look at specific branch of state rather than whole state.

Instead of absolute

When user data is created, the admin field is set to "false" (string) instead of false (boolean). This results in the database rules not working as intended (no major breaking changes however).

AC:

• admin field is initialized to a boolean instead of a string

Acceptance Criteria

1. Changed sidebar to look like the design mockup in the Wiki https://github.com/calebhsu/CoMake/wiki/Page-Designs
2. Incorporate Ian's slider into sidebar

Acceptance Criteria

1. Figure out how to get images to rotate

Acceptance Criteria

1. Implement mock sidebar for canvas page per Zach's mockups
   1.1 Make it look similar to Google Drive's sidebar

Acceptance Criteria:

• The response to a client's request will indicate if an email wasn't found

Actions & anything with a state.
By Tuesday

Implement the canvas creation service in the backend.

Acceptance Criteria:

• A canvas creation service will be made that handles user requests to create a canvas
• The client service package will be updated to create the proper request for the canvas creation service
• Front end add button is hooked up to backend creation

Acceptance Criteria

1. Get backend service to work with Share modal in front end

If possible, switch over, have client send fb tokens, and auth with firebase.

If not possible, figure out how to proceed.

Implement the canvas sharing service in the backend.

Acceptance Criteria:

• A canvas sharing service will be made that handles user requests to share a canvas
• The client service package will be updated to create the proper request for the canvas sharing service

Acceptance Criteria

1. Redux stuff
   1.1 Rest request from client to backend

Acceptance Criteria
1.Complete front-end / back-end to allow user to retrieve model image from CraftML

Closes #84, #119

Acceptance Criteria

1. Make it work

Acceptance Criteria

1. Mock Firebase for testing purposes
   1.1 Look into MockJS

Acceptance Criteria

1. Start making placeholder cards as discussed for home page
   1.1. Include the detail overlay / popup

This is mostly for proof of concept / making it easier to hook into backend once we actually have models.

Acceptance Criteria

• The current user's uid can be accessed from the user store

Acceptance Criteria

Do it

Acceptance Criteria

1. Profile information (on navbar) should update on login

Acceptance Criteria

1. When user clicks "Sign Out", they shouldn't be logged back in automatically.
2. Maybe ask Tom about this

Acceptance Criteria

1. Make second nav toolbar on canvas page
   1.1. Should be full-sized

Acceptance Criteria

1. Login button on front page should trigger login modal / popup
   1.1 Login should work
   1.2 If time, logging in should create a user in the DB
   2 Remove extra array from providerData database

Acceptance Criteria:

1. Create modals for canvas share, code export
2. Update home page
   2.1 Include placeholder canvas preview cards
3. 3D preview placeholder

Acceptance Criteria:

• The front-end should handle the case when a null or undefined property is supplied to a CanvasElement (ex: initLoc), and supply a default value

Get it to push to Firebase

Acceptance Criteria

1. Get backend code export to work with front end export modal

Users should own their canvas.
BLOCKED: #15, #11