🐛 BUG: Data from Custom hook does not re-render when data loads

[tyler-morales]

In the Game Activity tile, the expected behavior inside the "GAME ACTIVITY STATS" should read out the current date and the number of games played on that date.

Currently, when I call the custom hook to fetch the number of games, the hook only returns 0 even when there exist games. The number of games only appears if a user clicks the day in the heatmap. The number of games should appear on page load for the current date.

The file that needs fixing is ChartHeatmap.js and you might want to look at useLoadSpecficRecords.js

Acceptance Criteria:

• The current day should read out the data (whatever the current day is) and the number of games played during that day.

Below: This is incorrect. The number of games played should be 2. 2 only appears once October 22 is clicked in the heatmap.

Let me know if you have any issues or questions. You'll need an aws-exports file if you work on this issue. That can be found in the other current issue in this repo.

[inovux]

Heya @tyler-morales Can I look into this :)?

[sashank002]

hey @tyler-morales can i try this ?

[YasarArafathAli]

#53 Hey @tyler-morales... Can I have a look into this??

[tyler-morales]

@inovux yes, you can work on this

[inovux]

@tyler-morales awesome thanks! I tryed running the project, locally but it seems like it wont let me start it. Is there anything that I have to set up before running start?

[tyler-morales]

Yes, check out my comment with an aws-exports file here
#29

Let me know if you have any further issues

[inovux]

@tyler-morales awesome thanks lemme try!

[inovux]

@tyler-morales I dont think this will be fixable with the current infrastructure of the app. It is re-rendering a lot in unexpected ways.

I would suggest having a container or global store to hold the state of the app. The main problem now is that the hooks are using asynchronous functions and the data of the asynchronous functions is checked again with other asynchronous hooks inside the component. This probably needs some changes e.g. passing properties to the Grid components instead and managing the state in the parent of the Grid component.

Let me know if you think its a good idea to rework the way the state is managed right now. If you think there is a solution to this bug with the current infrastructure let me know what you have in mind :)

[tyler-morales]

Thanks for your help @inovux. I appreciate you going through my code and taking the time to look for a possible solution.

This is the largest codebase I have ever worked on and the first time I really dive into React. Because of this, I am totally open to hearing about new and better ways to organize the app's state.

I spend too many hours trying to get my custom hooks to work together all the while being asynchrous, so if you want to update any parts of this, I am happy to hear you!