Closed rngadam closed 6 years ago
Fixed this by adding
(orderBy: [ENTRY_YEAR_DESC, ENTRY_MONTH_DESC])
to the allMonthyGrosses
query
How is looks now on my local machine:
Hoping to get a reminder about how to make the production build live on dashboard.coderbunker.com
Did you break the current release?
Where's the pull request for this fix?
Why is there a PR on this repo that wasn't reviewed/merged first?
https://github.com/coderbunker/timesheet-dashboard-react/pull/7
You pushed the whole master branch to gh-pages instead of just the public subdirectory which is why it broke.
That's also why you need a README.md in your projects with deployment instruction
Last time I did this I created a production build and deployed it I'm assuming I should repeat this process again to get is working? https://codeburst.io/deploy-react-to-github-pages-to-create-an-amazing-website-42d8b09cd4d article of steps I took was given to my by alex essentially on local gh-pages branch, running npm run build and then npm run deploy
Ok so running those commands brought the site back online but did not incorporate the orderBy fix
please advise
did you pull first?
You had forgotten the part where you need to push the subdirectory, not the root. I just did.
document the other build steps in the README.md
You forgot the part where you need to push the subdirectory, not the root. I just did.
document the other build steps in the README.md
Fixed:
After an update to the latest data, I'm getting months in seemingly random order:
Maybe the GraphQL is missing an orderBy and the code is assuming the data is in order?
The data appears correctly in https://data.coderbunker.com