V9: Custom Component Recipe

[blendsdk]

Hi,

Please provide some examples of how we should create custom components the V9 way? (ComponentProps, Slots,renderers,.....)
I have created several custom components (some complex and large) I would like to migrate these to v9.

Thanks.

[micahgodbolt]

For downstream components built on v9, there is no hard requirement that you use component props, slots etc. These are conventions that we are using to keep our components as customizable as possible.

As for how we build v9 controls, one way to see our current best practice is to clone our repo and use the yarn create-package and yarn create-component commands. As we refine our approach, we move our best practices into those templates.

[blendsdk]

@micahgodbolt, thank you for your answer. I have been studying the react-components code in the hope of creating and migrating my v8 components to v9, following the MS style and standards. I would like to know why several of the functions (also in the template) are postfixed by _unstable?
What is the significance of this?

[blendsdk]

I must say I quite like this approach. It keeps the inner workings of a component logically separated. One nice-to-have would be to be able to restrict the type of the components that is accepted by children to be of a certain type. I am redesigning my v8 AppBar, AppBarLauncher and the AppBarPanel components with this approach. It opens lot of possibilities for composition and a plug-n-play behavior.

Would it be possible to get a heads-up when this api in changed?

[micahgodbolt]

We will certainly make a large announcement when we do have a final recomposition API. Our current focus right now is just getting more controls out the door.

[blendsdk]

@micahgodbolt. Thank you. Any idea when you except the recomposition API to be stable? Do you except major changes?

[micahgodbolt]

no hard plans yet. maybe this year? Depends on how components go and the demand for better recomposition. We don't expect it to be a major release due to existing API being unstable, but the final API will probably look very different than our existing (or be an abstraction layer on top of the existing)

[blendsdk]

Thank you. I guess for now I have to continue using this API. I hope you do not change it too much. Once you get the hang of it, it is very intuitive to work with.