We have noticed that the leaderboard incorrectly ranks Farmers when sorting by total wealth, under certain conditions.
Expected Behavior
Clicking on the "Total Wealth" table column on the leaderboard should sort the Farmers from least to greatest wealth, and clicking it again should sort from greatest to least wealth.
Current / Observed Behavior
When a farmer has between $0 and $1000 (non inclusive), we notice that they are inaccurately sorted on the leaderboard.
Sorting from greatest to least should have put the first 2 farmers at the very bottom of the list, instead it puts them at the top.
We see this when sorting from least to greatest:
The farmers with $100 and $199 should have been ranked at the top of the leaderboard for having the least wealth, but they do not appear until the very bottom
The issue is probably one related to sorting "strings" vs. sorting "numbers", and will involve having to understand internal details of the OurTable component.
Recognize that the OurTable component is used in many places in the application, so you need a solution that doesn't involve putting specific special case code into that component.
Have you updated the title?
Summary
We have noticed that the leaderboard incorrectly ranks Farmers when sorting by total wealth, under certain conditions.
Expected Behavior
Clicking on the "Total Wealth" table column on the leaderboard should sort the Farmers from least to greatest wealth, and clicking it again should sort from greatest to least wealth.
Current / Observed Behavior
When a farmer has between $0 and $1000 (non inclusive), we notice that they are inaccurately sorted on the leaderboard.
Sorting from greatest to least should have put the first 2 farmers at the very bottom of the list, instead it puts them at the top.
We see this when sorting from least to greatest:
The farmers with $100 and $199 should have been ranked at the top of the leaderboard for having the least wealth, but they do not appear until the very bottom
Steps to Reproduce
Discussion
The issue is probably one related to sorting "strings" vs. sorting "numbers", and will involve having to understand internal details of the OurTable component.
Recognize that the OurTable component is used in many places in the application, so you need a solution that doesn't involve putting specific special case code into that component.