Dash all-in-one component compatibility? #403
Description
Problem
I was wondering what is the plan for crystal-toolkit to transition to the Dash all-in-one component convention?
MP website is trying to implement the changes, but it would need crystal-toolkit to move together in this direction. So just wondering what in your opinion is the easiest path for ctk to adopt the changes.
Proposed Solution
MPComponent doesn't accept dictionary convention as its id name. CTK needs to be able to accept both dictionaries and strings for 1) AIO convention and 2) backward compatibility with existing components.
Alternatives
No response