{"id":2381,"date":"2025-12-03T01:13:57","date_gmt":"2025-12-03T09:13:57","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=2381"},"modified":"2025-12-03T04:30:36","modified_gmt":"2025-12-03T12:30:36","slug":"extendings-signals-frosm-with-a-custom-directive","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/extendings-signals-frosm-with-a-custom-directive\/","title":{"rendered":"Extending Signals Forms with a custom directive"},"content":{"rendered":"\n

I decided to do something different for this newsletter: a video tutorial (about 12 minutes long) instead of a blog post. If you like that format, please let me know. I might use this once or twice per month from now on if you like it.<\/p>\n\n\n\n

The goal of the video is to re-enable form CSS classes<\/a> such as ng-valid<\/code>, ng-touched<\/code>, ng-pristine<\/code>, etc., in Signal Forms since that feature is absent from the API at the moment. <\/p>\n\n\n\n

It’s a great example of creating a custom directive<\/a>, which isn’t something developers do every day, making it an even more interesting tutorial:<\/p>\n\n\n\n

\n