As a dev, I want to download propTypes so that I can add them to my components.
Acceptance Criteria
How will we know that the user story is complete?
As a dev, when I put in a false data types in a variable, I will see a helpful error in my console telling me that it was expecting an array of objects rather than an array of numbers.
As a user, I want to click the top 100 button so that I can see a checklist of possible birds.
Acceptance Criteria
How will we know that the user story is complete?
As a sighted user, when I click top 100 I see a list of top 100 birds in the area. I am able to click the check marks. Upon refresh, the check mark doesn't persist.
Concerns
When checked, it pushes into the "sighted" array existing in another components (later)
will eventually apply Details, but for now, it's not needed.
As a dev, I want to apply cypress testing so that I can ensure user flow from home to top 100 and then home to personal sightings is functioning as expected.
Acceptance Criteria
How will we know that the user story is complete?
As a dev, when I apply fixtures and sub api calls to test this user flow, all my related tests will pass.
Concerns
if I don't need to stub data for my mock files, should I just use the mock files or something smaller?
As a user, I want to go to the home page so that I can see a static view.
Acceptance Criteria
How will we know that the user story is complete?
As a sighted user, when I visit the home page, I will see a header, a navigation bar, and a bird yet seen highlight. When I try to click on one of the nav buttons, nothing happens. When I try to click a bird yet seen, nothing happens.
As a dev, I want to ensure on refresh that a user never sees an unfriendly error.
Acceptance Criteria
How will we know that the user story is complete?
As a user, when I click refresh several times on the homepage, I am either greeted with an error message of a cute owl or I see a newly randomized bird.
Concerns
Is the refresh consistent?
Does it happen because a call is being done too often?
As a dev, I want to apply SASS so that I can utilize variables and mixins to minimize redundancy in styling.
Acceptance Criteria
How will we know that the user story is complete?
As a dev, when I open the project, I can see in the file structure sass files and partial files. I see that inside of component files, sass variables and mixins are being imported and applied.
As a user, I want to see images so that I can know what the bird looks like.
Acceptance Criteria
How will we know that the user story is complete?
As a dev, I will see in the data folder a file with an array of objects that contain two properties: img url & bird code.
As a user, when I go to the details page or when I am on the highlight page, I will see an image of the appropriate bird.
As a dev, I want to mock sighting data so that I can simulate app behavior if a user was able to interact with the app & post data to the server.
Acceptance Criteria
How will we know that the user story is complete?
As a dev, I will see a data folder with a file containing mocked "sighting" data of the same format as the API data.
As a user, I will see a list of birds that I've seen and on what date.
As a user, I want to see an about page so that I can learn more about the developers of the app.
Acceptance Criteria
How will we know that the user story is complete?
As a sighted user, I can click the "About" page and read about the developer, their motivation, see their lifelist, and links to other social media sites if I want to get in touch.