-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Stop calling deprecated Connection functions push_connection
, pop_connection
, resolve_connection
, parse_connection
#1949
base: master
Are you sure you want to change the base?
Conversation
connection is called explicitly whilst retaining backwards compatibility with push_connection
if
is equal to
need to 🤔 think of how I can apply this to |
push_connection
push_connection
, pop_connection
, resolve_connection
, `parse_connection
not sure if this is the best way to replace connection but lmk
@ccrvlh I see you added the deprecation comments a while ago, I am trying to solve this issue however there is nothing clear in the docs or your PR to suggest how we should use connection explicitly instead of the Connection functions, any comments or suggestions would be greatly appreciated. |
push_connection
, pop_connection
, resolve_connection
, `parse_connectionpush_connection
, pop_connection
, resolve_connection
, parse_connection
Hi @PrenSJ2. In the PR #1860 there's a description about what was done:
The docs also discuss ways of handling connections here. When we worked on that PR, the connection It would probably make sense to also add a deprecation warning to the docs, and slowly refactor the internals to use the explicit connection handling pattern everywhere (mostly the
I don't remember the details and every case where the connection is being Unfortunately I haven't been having much time to work here (hopefully that will change in the future), but let me know if you have any doubts, I'll try to help as I can. |
I don't think we should change this behavior until version 2.0, where |
Fix #1948