-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate and remove OBSERVE_REQUEST_CALLBACK
#1886
Comments
With the addition of the UPDATE_ON_FETCH setting, the OBSERVE_REQUEST_CALLBACK setting is redundant. Thus add a check debug_toolbar.W008 to warn if it is present in DEBUG_TOOLBAR_CONFIG, but do not remove it yet. See django-commons#1886
With the addition of the UPDATE_ON_FETCH setting, the OBSERVE_REQUEST_CALLBACK setting is redundant. Thus add a check debug_toolbar.W008 to warn if it is present in DEBUG_TOOLBAR_CONFIG, but do not remove it yet. See django-commons#1886
With the addition of the UPDATE_ON_FETCH setting, the OBSERVE_REQUEST_CALLBACK setting is redundant. Thus add a check debug_toolbar.W008 to warn if it is present in DEBUG_TOOLBAR_CONFIG, but do not remove it yet. See django-commons#1886
@tim-schilling this issue could be marked as closed. |
This deprecation warning appears to suggest that we can remove However, that's not the case, because it would break the following: Moreover, it is not clear to me from the message/docs/PR whether the default values for |
@dennisvang If you're attempting to have the toolbar reflect the latest request being made, including the AJAX requests while you're on a page, set |
@tim-schilling Thanks for the explanation. My point is that we now get a warning if |
@dennisvang It should only log a deprecation warning if you include it in your project's settings' If you're getting a |
@tim-schilling Thanks, you're right: It turns out we had Sorry for that. |
With the addition of
UPDATE_ON_FETCH
from #1843, we no longer need to keepOBSERVE_REQUEST_CALLBACK
around. The functionality that can be implemented with that can be redone inSHOW_TOOLBAR_CALLBACK
as indicated by @living180 hereThe text was updated successfully, but these errors were encountered: