Organizations, Priorities, Events/actions all need real round trips in the components

There should always be a neighborhood selected when we are on the priorities page. It needs to show on this page, per designs

What kind of tests do we want to prioritize?

From what I see on PrioritiesOrderPage.js we are able to promote/demote priorities. But this only reflects the local state of our app. It doesn't actually change anything in the database. Any idea, if the endpoint on the API exists for this?

Currently there's no styling. It should follow the designs and be consistent with the rest of the app

The actions page says “Future Events,” and it should say “Actions Taken.”

Some footer should be added to refer people back to the source code, and to Code For Sacramento

Add a link somewhere on the Events list page that takes us back to the priorities page

Currently, we have Post and Action files. (Post, PostPage, PostPage.test) They should all be named Action/Actions but as we are writing styling and the other pages, some are still using the Post files. The test page is also for Post, not PostPage.

I've tried to remove the Post files and rename everything to Actions, but we have a few branches out that look like there updates to post. So I'm suggesting we:

• Make sure all open/current branches with are merged with changes to the Post and/or Action files.
• Rename styles and imports all in a single PR, along with deleting the old.

I think this would ensure we have the correct naming conventions going forward.

Currently, the organization id is saved to localstorage when the organization is selected, but it's not read by the app to set the org when the page loads.

I made an issue on the api repo about some of the things that need to be resolved, but eventually, we need to replace the hardcoded values for the following in NewActionForm.js :

• user_id
• action_type_id
• visibility

They are currently hardcoded in so that the DB accepts the request. We have no docs outlining the required fields right now, so we are sending all fields.

A lot of our linters are formatting differently. Makes PR's more confusing.

Right now if we successfully submit a priority or action, there's no indication of it.

The API has a /types endpoint which returns priority types.

The NeighborhoodSelector is still using a hardcoded (from the seed.js file) set of priority types.

Use the code in AddPriorities page to get the real priority types and populate the list with those. Then it's time to remove the types from the seed.js

Need to discuss this. Do we allow it? Maybe we only show five but allow more so the admins can have a “backlog” of lower priority issues.

Currently the README is jut the standard NPM instructions. Nice, but we have lots of details already about how to stand up the project locally, connect it to an API, etc. And we should have a blurb at least which describes what this project is. Describe Neighborhood Connect

The placeholder in the org list is by design, but we need to update it. Until we have a map built, or something much better than a list of organizations to draw from, it is easier for users to see all existing organizations until they filter them. If they hav Eno idea what neighborhood to select, they can at least scroll through all neighborhoods, this way.

Check the console on the Priorities page. There is a warning about OrgId being passed as a number when it was expecting a string.

Need the following POST/PATCH:

• POST Actions (event)
• POST Priority

As of 7/26 there are no POST or PATCH routes in backend API.

When leaders drag a priority up or down, the app needs to send patches.

But, what about a new endpoint that we post to that just represents a new rank of five:
/orgs/43/rerank
{[ 999,24, 33, 77, 8]}

Currently the forms send raw data to the back end. We need to do some type of purification so the back end does not receive dangerous data, such as dropping a table within the body text.

Does anyone have a copy of the Sketch file that was made during the hackathon? Not sure where to find that. Also, I don't have Sketch, so a PDF copy would be 💯.

/addNewPriority route shows page but there's no styling

On line 24 I am logging neighborhood, it is coming in as undefined. So, when we pass it as props to the component that holds the current location: <LocationHolder hood={neighborhood} /> it does not receive a title for neighborhood.

The icon in the header is empty, and the search results lines should be styled to match the designs ... bordered with white interior. see design sketches

Right now the front end has localhost hard coded. Need to be configurable

Same priority issues exist among organizations. Should we share the record, links them, copy them? Note that different associations will see the same problem at a different rank