Why I think Component-Driven Development needs a rethink in the Signal era
The article discusses the need to rethink Component-Driven Development (CDD) in light of Angular's new signal-based architecture. It highlights how traditional assumptions about component inputs being plain properties are no longer valid. The author argues that existing tooling may not adequately address the changes brought by signals, leading to potential issues in component rendering.
- ▪Component-Driven Development assumed a render model that signal-based Angular has left behind.
- ▪The way CDD thinks about components is based on inputs being plain properties, which is no longer the case in Angular.
- ▪Existing tools like Storybook may not be solving the right problem due to the shift in how component inputs are handled.
DEV.to (Top) files mainly under programming. We currently carry 4,900 of its stories.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3909446) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Alex Posted on May 18 Why I think Component-Driven Development needs a rethink in the Signal era #angular #typescript #storybook #webdev Component-Driven Development assumed a render model that signal-based Angular has quietly left behind. The tooling has not caught up, and I am not sure simply patching it will be enough.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
