{"version":"2.1.267","anchor":"render-tree-now-handles-a-client-component-type","canonical_anchor":"render-tree-now-handles-a-client-component-type","heading":"Render tree now handles a 'Client' component type","tier":"internal","area":"Plugin UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/render-tree-now-handles-a-client-component-type","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Render tree now handles a 'Client' component type\n\nPlugin UI rendering adds support for a new 'Client' component type\n\n**Unclear.** What a 'Client' component type represents or looks like in a plugin's UI is not stated.\n\n**What**\n\nThe function that walks a plugin's UI render tree (used for both rendering and permission checks) now has a dedicated branch for a component of type `Client`, handling it before falling through to the generic children-recursion or the existing Button\/Input\/Select handling.\n\n**Why**\n\nThis adds support for a new kind of UI component in plugin interfaces, though what a `Client` component represents or renders as isn't stated.\n\n- Area: Plugin UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}