-
Notifications
You must be signed in to change notification settings - Fork 59
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
add support for kwargs in instance init #372
Conversation
now instance() and context.create_instance are interchangable, before it would error out since only some kwars were shared.
just discovered the dev docs so PR likely will need some work |
Thanks @hannesdelbeke! Yes, the main thing missing here are tests. Something to make sure it works the way you expect, and something to make sure it breaks when you expect it to. The fact that all prior tests pass is great, it means we haven't broken anything anyone depends on. Other than that, I'm onboard with this change; normally I'd never actually use the |
cheers, will look into when I have time. |
probably because curently pyblish is context heavy, and parent support is still early days. |
That's true, there's a place for hierarchical instances but so far nobody has taken on the challenge. If there isn't yet an issue about this, now would be good time to open one so we can sort out the details. Such as, should the next parent continue if the child of a prior parent fails? |
i'll probably follow up on that in an issue when i have time since it aligns with my goals for pyblish. |
i've added a test testing the new setup. |
Success! Great work @hannesdelbeke. :D |
now instance() and context.create_instance are interchangable, before it would error out since only some kwars were shared.
see forum post explaining it https://forums.pyblish.com/t/instance-vs-create-instance/658