Elevator Pitch is a site to organize group projects based on ideas, rather than individuals

This will add functionality for an idea owner to abandon an idea (rather than outright delete), and free it up for another space member without any prior ideas/approvals to claim it as their own.

• [x] test resource.js front end code
• [x] test resource.js back end api routes

Should work with resourceMini.handlebars (modal for adding resources) Resolves #61 #85 #86 #

https://www.loom.com/share/ddc4f6a98b534c5b9682b42f7b8c3e43

Added internal script to idea.handlebars, no existing js file for this view. Can create new idea.js file if that is cleaner.

Resolves #62

TODO

• [x] Create view
• [x] Create JS to make request access POST request
• [x] Create /api/space/:space_id/member to create a new SpaceMember entry
• [x] Add button link to /space/:space_id/access on the main space page

closes #30 closes #35

Added homeroute and handlebars for a detailed view on an Idea called by its ID. Includes a VERY basic comment section (with no way to actually comment yet haha)

• [x] /login and /signup functionality complete with handlebars and js
• [x] logout functionality complete
• [x] Nav complete with auto login/logout change
• [x] Nav modal added
• [x] Footer github link added
• [x] homepage handlebars complete
• [x] Entering a space id on homepage
• [x] - [ ] Creating a space name on homepage

Let's test edit/delete a resource...

• [ ] After adding an image, a button should show on the card for delete.
• [ ] After adding a link or markdown, two buttons should show - edit / delete.
• [ ] Edit/Delete buttons show on idea view and in the resource view**
• [ ] Delete - simple client side click event with basic confirm message to make sure you intend to delete. Sorry, I know it's basic ;)
• [ ] Editing an existing markdown/link should show a modal with current content.

• User should be able to edit name and content.
• Submit should render a successful toast message and updated content.

** Only idea owners delete/edit resources. Let me know if this should be the resource owner. But if an idea owner can't moderate that could be a problem as well. Maybe it should be both of them could edit/delete? Just lmk

Hey @jmichaelbrown8 , before we do the rebuild of the production database, can you update the Idea.user_id foreign key to allow NULL?

My next batch of updates is going to enforce that a user can only have a single approved idea for a space to prevent people from being accepted to multiple spaces, but I still want users to be able to submit multiple ideas.

So my thought is to allow the user to mark an option on the create idea form that will create the idea as "unclaimed" by leaving the user_id field NULL. So they can still throw out new idea and see if people like it and allow other to pick it up if they want.

This will also allow us something like an "Abandon" idea feature so, an owner can leave an idea without deleting it, and other users can come claim it.

This PR adds new features to detect if a user has approval for an idea within a space and adds constraints to views and api routes to prevent a user from joining a new idea, if they are already an approved member of an exist idea.

Notes for Reviewer

• Main query logic to fetch data used in validation is built in to static model methods. See Idea.getStatus and Interest.findUserApprovalInSpace

Reviewer Check List

If the logged in user owns an idea or has been approved to collaborate within an idea for a space

• [x] Logged in user will not see "Add Idea" on the space page
• [x] GET /space/:space_id/ideas redirect logged in user will be redirected back to the space page
• [x] POST /space/:space_id/idea/:idea_id Should error for logged in user
• [x] Logged in user should not see "join features" within any ideas of the space.
• [x] POST /:space_id/idea/:idea_id/interest Should error for logged in user
• [x] PUT /:space_id/idea/:idea_id/interest Should error for logged in user

If the owner of an idea

• [x] Should not see records of users approved for other ideas within management tools.
• [x] PUT /:space_id/idea/:idea_id/interest/:user_id with `{ "status": "approved" } Should error for logged in owner of idea.

This morning I was able to get the like button to fire. There seems to be an issue with the ideaUpvotesRoutes in the controllers folder. I was getting a 404 error back when I tried using "/api/upvote" in insomnia. And in the browser console when I clicked the like button. Shout out to Kim for sitting with me while we tried to figure this out.

#32

This is relatively low-risk since we don't have real production data yet, but this outlines how we might go about schema changes in the future (and brings us up to the current schema needed to support the Idea.members and Ideas.skills columns).