You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
add logic to search for a ., if so, parseFloat instead?
for array thing: we will update frontend to properly send an array of counties so we don't need to do string split anymore bc express and axios hadle that
The text was updated successfully, but these errors were encountered:
revision: specifyqueryfetch needs complete overhaul. queryfetch needs to know how to parseFloat.
jeffzyliu
changed the title
specifiedQueryFetch should not always use parseInt
queryFetch should not always use parseInt
Apr 13, 2023
jeffzyliu
changed the title
queryFetch should not always use parseInt
queryFetch should not always use parseInt, should not string join to array
Apr 13, 2023
add logic to search for a ., if so, parseFloat instead?
for array thing: we will update frontend to properly send an array of counties so we don't need to do string split anymore bc express and axios hadle that
The text was updated successfully, but these errors were encountered: