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
With the changes in #14 , the filter now defaults to America only. So when we need our end users to test, we have to get them to manually check the filters, increasing the number of steps... They're also not sure what they're ticking -- they're end users.
Can the filters be set using a GET or Hash identifier? This will more allow us to provide pre-configured links to our end users and get results more easily.
The text was updated successfully, but these errors were encountered:
With the changes in #14 , the filter now defaults to America only. So when we need our end users to test, we have to get them to manually check the filters, increasing the number of steps... They're also not sure what they're ticking -- they're end users.
Can the filters be set using a GET or Hash identifier? This will more allow us to provide pre-configured links to our end users and get results more easily.
The text was updated successfully, but these errors were encountered: