Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a member, I can see a list of all slack channels in the archive. #11

Closed
12 tasks done
pconrad opened this issue Nov 17, 2020 · 2 comments · Fixed by #16
Closed
12 tasks done

As a member, I can see a list of all slack channels in the archive. #11

pconrad opened this issue Nov 17, 2020 · 2 comments · Fixed by #16
Assignees
Projects

Comments

@pconrad
Copy link
Contributor

pconrad commented Nov 17, 2020

Acceptance Criteria

  • There will be a top level menu item called Channels
  • Only members will be able to see that menu item
  • That menu item goes to page that lists all of the channels.

Implementation Todos

Front end:

  • Add "Channels" to top nav, for members/admins only
  • "Channels" on top nav should link to a page (create the page under /javascript/src/main/pages and add it to App.js as a AuthorizedRoute)
  • The page should link to a component (added under /javascript/src/main/components) that uses BootstrapTable to display a list of channels, initially fake hard coded channels.
  • Once the backend routes are in place, instead of fake hard coded channels, display the real channels. This involves using useSWR to get the data from the back end.

Back end:

  • Add a ChannelRepository class that corresponds to the channels collection in the MongoDB database.
  • Add a ChannelDocument class that corresponds to the document (the JSON object) for each channel.
  • Add a ChannelsController class that creates API routes for channels. It should have a route /api/members/channels that is available only to members/admins that retrieives a list of channels.

Testing:

  • Front end test coverage should be as close to 100% as possible (from javascript subdirectory, use npm run coverage)
  • Back end test coverage should be as close to 100% as possible (from top dir, use mvn test jacoco:report -Dskip.npm)
@pconrad pconrad created this issue from a note in F20-Staff (In Progress) Nov 17, 2020
@pconrad pconrad self-assigned this Nov 17, 2020
@pconrad
Copy link
Contributor Author

pconrad commented Nov 17, 2020

branch staff-channelList

@pconrad
Copy link
Contributor Author

pconrad commented Nov 17, 2020

Next steps are to work on the backend routes.

pconrad added a commit that referenced this issue Nov 19, 2020
* Added front end component for page and table for channels
* Added backend document, repository, and controller for channels
@scottpchow23 scottpchow23 moved this from In Progress to In Review in F20-Staff Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
F20-Staff
In Review
Development

Successfully merging a pull request may close this issue.

2 participants