Uh oh!
There was an error while loading. Please reload this page.
Component as props - #1965
Conversation
8f4373f to
3905100CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
# Conflicts: # dash/development/base_component.py
…andle children props.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| @classmethod | ||
| def _get_base_nodes(cls): | ||
| if not cls._base_nodes: |
There was a problem hiding this comment.
if a component has lots of props but none of them accept components, will we run this iteration every time one of them is instantiated? If so, can we avoid that? Moving + ["children"] in here would be one way perhaps?
There was a problem hiding this comment.
oh sorry, it's only iterating over _children_props - so the problem only comes if there are lots of nested props and no base props. Still would be best to avoid.
There was a problem hiding this comment.
Let's move that to the generator.
There was a problem hiding this comment.
Looks great! Seems like the way you implemented this is compatible with the old generated components, how hard would it be to add a test to explicitly verify that? ie include a component in the tests that doesn't auto-generate but instead uses the old generator output?
There was a problem hiding this comment.
Added a legacy test from the old standard component output.
alexcjohnson
left a comment
There was a problem hiding this comment.
Looks great! Add a changelog entry and consider my minor perf comment and I think we're ready to go! 💃
Add component as prop support.
Contributor Checklist
optionals
CHANGELOG.md