Skip to content
This repository was archived by the owner on Jul 7, 2022. It is now read-only.

mq-5/github-issue

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

49 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CoderSchool FTW - GEThub

Created with love by: Your Name Here

View online at: Your URL here

One or two sentence summary of your project.

User Stories

The following required functionalities are completed (this is a sample):

  • The user can enter a repository in a search bar, click "search", and see the associated issues. The repository should be of the format owner/repo-name, e.g. facebook/react.
  • If the repository does not exist, the user should see a proper error message.

The user should be able to see the following information for each issue:

  • Issue Title
  • Number of the issue
  • Owner of the Issue
  • Owner Avatar
  • How long ago the issue was created in a human-friendly format (e.g. 2 days ago)
  • Body of the Issue
  • Label - note the color as returned by the API.
  • State of Issue (Open/Closed).
  • The user should be able to see multiple pages of results, by clicking a pagination control.
  • The user should be able to see the body of the issue rendered in markdown.
  • The user should be able to create a new issue via a modal for the repository, by clicking on a "new issue" button. Clicking on this button will pop open a modal that asks for the requisite fields.
  • If there is an error creating the issue (for example, the user not supplying all required parameters), there should be a nice error message to the user.

The following optional features are implemented:

  • The user can see more details (including comments!) in a modal that's opened by clicking on the title of the issue.
  • The user, upon opening this modal, can add a comment via a textarea at the bottom of the page.
  • The user, upon opening the modal, can close the issue. If the person does not have the appropriate access to close an issue, the user sees a nicely formatted error message.
  • The user can see reactions attached to each comment (Reactions API).
  • The user can add reactions to a comment (API documentation).
  • Input Fuzzy Matching: the user should be able to type in either https://github.com/facebook/react or facebook/react, BOTH should work.

Instead of using Modal to show issue, use React Router (link) to navigate to different URL issues/:issueId to display the full issue. Have the Back button to go back to the previous page (from the individual issue page).

Time Spent and Lessons Learned

Time spent: 20 hours each by 4 team members.

License

Copyright 2019 - FTW El Captain

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •