-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Forward select Rectangle kwargs to Connection patch #24082
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
Conversation
c31fc6f
to
6a67b8e
Compare
Thanks! Can you please add a test? I think a suitable test is to set some of the parameters and then check that the resulting ConnectorPatch have the expected values. |
Yes I can add a test. Is there a specific place where I should create it? |
I think that |
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Hi @ejmercier are you still interested in working on this one? It looks like it still needs a test. I'm going to mark this as "draft" for now. Please mark it as "ready for review" when you are ready. In the meantime, if you need help, feel free to ask questions here. Or you may prefer to ask them in our incubator gitter room. |
@rcomer thanks for checking up! I'm still looking to work on this. I'll plan to write the test soon and move it out of drafts! If I have any questions I'll reach out |
The target issue here has now been addressed as part of a larger change in #27996. Thank you for your work here @ejmercier. |
PR Summary
Closes #23424
This bug fix forwards
**kwargs
from the indicate_inset function into theConnection Patch
. It uses a blacklist to decide which ones should be passed aspatch_kwargs
to theConnection Patch
and not theRectangle patch
.PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).