Template CONTEXT for the composerExtra slot — host UI rendered directly ABOVE the
composer, wherever the chat area shows one: the conversation's composer, the
new-conversation composer, and the built-in empty state's composer.
Like headerActions this is a template-context shape, not a component contract: project
an ad-hoc <ng-template mjChatSlot="composerExtra" let-conversation let-busy="IsProcessing">.
Nothing renders in that spot when no template is projected, so the default layout is
unchanged. Its keys are PascalCase, per MJ's naming rules for new public members; the older
headerActions context keeps its camelCase keys.
Template CONTEXT for the
composerExtraslot — host UI rendered directly ABOVE the composer, wherever the chat area shows one: the conversation's composer, the new-conversation composer, and the built-in empty state's composer.Like
headerActionsthis is a template-context shape, not a component contract: project an ad-hoc<ng-template mjChatSlot="composerExtra" let-conversation let-busy="IsProcessing">. Nothing renders in that spot when no template is projected, so the default layout is unchanged. Its keys are PascalCase, per MJ's naming rules for new public members; the olderheaderActionscontext keeps its camelCase keys.