You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: merge_init_into_class does not merge overloads #212
Thanks for the report @kaktus42. Even though we could consider it a new feature, the behavior doesn't match what the user can expect, so I'll mark this as a bug.
Here is how I see things could be rendered:
separated signatures: render all signatures, just like for functions
heading-signatures: render the implementation signature in the heading, then further code blocks for each overload. I'm open to other suggestions, if you have any!
This will bring rudimentary support for such cases. We have other issues in our backlog to improve support for overloads.
Activity
pawamoy commentedon Nov 26, 2024
Thanks for the report @kaktus42. Even though we could consider it a new feature, the behavior doesn't match what the user can expect, so I'll mark this as a bug.
Here is how I see things could be rendered:
This will bring rudimentary support for such cases. We have other issues in our backlog to improve support for overloads.
pawamoy commentedon Dec 3, 2024
Here's how it will look.
fix: Handle `__init__` overloads when merging into class
fix: Handle `__init__` overloads when merging into class