Created a linked button that is handled onClick. Everything is wired and functioning.
get-info button changes the url and displays new state (single-bird display).
*onClick for get-info button also shows the bird ID for filtering and displaying single-bird display
[x] New Feature
[x] Fix
[ ] Documentation
[ ] Tests
🧠 Context or Rationale for this code
What is helpful for team to know and understand about decisions made in this code.
Create a route that changes state for our last displayed state!
👀 Checks
[x] When the project is run locally, the terminal shows no errors or warnings
[x] Breaks nothing
[ ] Breaks some things & Creates new issues
[ ] Code in this branch has been tested
[ ] Forgot to write new tests for changes in this code, but it is added to the project board as a ticket.
[x] Code is DRY, reusable, follows SRP and trends toward function purity
[ ] I've updated the project board to reflect changes, add issues, or tickets
✍🏽 Notes, Questions, What's Next
Route is now ready to have new state plugged in!
By using the type assertion as HTMLButtonElement within our get info button - we are telling TypeScript that event.target is an HTMLButtonElement and can be used to access the id property. (Type Script Assertion)
🛠️ Description of this branch
Created a linked button that is handled onClick. Everything is wired and functioning. get-info button changes the url and displays new state (single-bird display). *onClick for get-info button also shows the bird ID for filtering and displaying single-bird display
🧠 Context or Rationale for this code
What is helpful for team to know and understand about decisions made in this code.
Create a route that changes state for our last displayed state!
👀 Checks
✍🏽 Notes, Questions, What's Next
Route is now ready to have new state plugged in!
By using the type assertion as HTMLButtonElement within our get info button - we are telling TypeScript that event.target is an HTMLButtonElement and can be used to access the id property. (Type Script Assertion)
Screenshot