Skip to content

Conversation

@droshev
Copy link
Contributor

@droshev droshev commented Jan 2, 2026

signalize and make zoneless title component, deprecate the module

@droshev droshev requested a review from a team January 2, 2026 18:12
@droshev droshev self-assigned this Jan 2, 2026
@droshev droshev added this to the Sprint 154 - January 2026 milestone Jan 2, 2026
@netlify
Copy link

netlify bot commented Jan 2, 2026

Deploy Preview for fundamental-ngx ready!

Name Link
🔨 Latest commit dff66be
🔍 Latest deploy log https://app.netlify.com/projects/fundamental-ngx/deploys/695da0364151f60008675272
😎 Deploy Preview https://deploy-preview-13698--fundamental-ngx.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@droshev droshev changed the title fix(core): signalize title component fix(core): signalify title component Jan 5, 2026
this._changeDetectorRef.detectChanges();
if (title && !title.headerSize()) {
// Get the component instance's ComponentRef for setting signal inputs
const componentRef = (title as any)._componentRef as ComponentRef<TitleComponent>;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am always a little worried when we have to do as any or any other type assertions.
Can we instead mark headerSize as model instead of input in the TitleComponent and do simply:

title.headerSize.set(5);

I, personally, find it easer to read. Also, that way we will preserve type safety. Do you see any drawbacks?

}
});
this._changeDetectorRef.detectChanges();
this._changeDetectorRef.markForCheck();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When you migrate to signal, please check if this is still needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we migrate the dialog in a separate PR?

@InnaAtanasova InnaAtanasova mentioned this pull request Jan 5, 2026
5 tasks
@MariaIDineva
Copy link
Contributor

Just one more thing that I noticed - in the documentation we still encourage the user to use TitleModule instead of the component. Maybe we should update that as well, like you did for the text component.
Screenshot 2026-01-06 at 10 37 28

@droshev droshev force-pushed the fix/title-signalize branch from a808d19 to dff66be Compare January 6, 2026 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants