-
Notifications
You must be signed in to change notification settings - Fork 406
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
refactor(middleware_factory): add from __future__ import annotations #4941
refactor(middleware_factory): add from __future__ import annotations #4941
Conversation
and update code according to ruff rules TCH, UP006, UP007, UP037 and FA100.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ericbn! What do you think about changing the examples related to Middleware Factory? I know there are dozens of files to change in all the other PRs you opened, but we can divide and conquer to make it faster. I can modify the examples and fix highlights, does that make sense?
@leandrodamascena, sure let’s divide and conquer, and you can modify the examples and highlights. Sounds great! I’ll take a look at the absolute imports soon. |
examples/middleware_factory/src/getting_started_middleware_tracer_function.py
Outdated
Show resolved
Hide resolved
5a28f8b
to
9db63ef
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
APPROVED! 🥇
Issue number: #4951
Summary
Changes
Add
from __future__ import annotations
to middleware_factory packageUser experience
Discussed in #4607
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.