QiDAO treasury address was incorrectly lower-cased, and next routes are case sensitive this caused 404 when logging into the dashboard using to login pop-up.
Solution was to add the address with the proper casing as well as wrap all SHAREABLE_ADDRESSES in toAddress('0x000...000') to allow for proper checksum in order to avoid this mistake in the future.
Now when an address that doesn't match casing is entered to the login popup the app correctly warns that the input address is not associated with any dashboards (and to contact us if they have questions about this). I feel this is the correct behavior.
Motivation and Context
Fix an issue I was seeing with QiDAO dashboard login
How Has This Been Tested?
Manually, confirmed that things worked as expected
Description
QiDAO treasury address was incorrectly lower-cased, and next routes are case sensitive this caused 404 when logging into the dashboard using to login pop-up.
Solution was to add the address with the proper casing as well as wrap all
SHAREABLE_ADDRESSES
intoAddress('0x000...000')
to allow for proper checksum in order to avoid this mistake in the future.Now when an address that doesn't match casing is entered to the login popup the app correctly warns that the input address is not associated with any dashboards (and to contact us if they have questions about this). I feel this is the correct behavior.
Motivation and Context
Fix an issue I was seeing with QiDAO dashboard login
How Has This Been Tested?
Manually, confirmed that things worked as expected