In https://github.com/cityofaustin/atd-data-tech/issues/19687, we added some basic error handling for outdated field in saved views or bookmarked urls to help users report any issues. We could further enhance this error handling with the following suggestions that came out of the review:
It might be nice to offer the user a working query string with the problematic piece removed (John, see above)
-☝️ on that note, it might be nice to make a customized fallback component instead of the generic Something went wrong, since we know specifically what went wrong. that might be a fun enhancement down the road (John, see above)
This will be so helpful to keep track of this type of error. Well as long as someone submits the ticket. What about in the future adding an Activity Metrics event...... I agree with John that a fun future enhancement could be a custom fallback component, especially since the feedback to "try refreshing the page" is not going to address this specific error. (Chia, see https://github.com/cityofaustin/atd-moped/pull/1480#pullrequestreview-2443784760)
In https://github.com/cityofaustin/atd-data-tech/issues/19687, we added some basic error handling for outdated field in saved views or bookmarked urls to help users report any issues. We could further enhance this error handling with the following suggestions that came out of the review: