Explicitly clear the cached views and memoized data for the user's
accounts and home pages following a successful account deletion. This
prevents stale data from appearing in the UI and ensures statistics are
accurately recalculated.
Update the `make_cache_key` function to include the request query string
in the generated key. This allows for manual cache busting by appending
version parameters to redirects.
In the `delete_account` route, replace manual cache deletion logic with
a redirect containing a timestamped nonce. This ensures that the user's
account list and home page views are refreshed without requiring explicit
knowledge of all internal cache keys.
- Added print statements to display current and new config values
- Improved visibility into config update process
- No functional changes, only added logging for debugging
- Pass authentication credentials to background threads for NPM updates
- Improve regex patterns for accurate location block matching
- Add support for creating new location blocks for streams
- Return success status from NPM config update operations
- Update test script to handle errors and apply changes automatically
When updating, adding, or deleting accounts, multiple cache entries need to be invalidated to ensure data consistency. This includes clearing both memoized and regular cache entries for user accounts and the home page, which displays account statistics. The changes ensure that cached data is properly refreshed across all relevant views.
Rename the `proxy_send_test_notification` function to `send_test_notification_proxy` for better naming consistency.
The corresponding template is updated to use `url_for` for the fetch request, making the URL generation more robust and maintainable.
