DEV Community

DEV Community is a community of 550,695 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create new account Log in
loading...

Discussion on: Angular - How many components is too many components?

View post Full discussion

Replies for: In our current project we've got this period component containing two date inputs, start and end. We're using it across the entire project in vario...

Collapse
antjanus profile image
Antonin Januska •

Oh yeah! Absolutely. But that's when I'd split it based on functionality. Conditionals usually indicate that you're trying to force one thing to fulfill the role of many.

You can also invert the validation and have the parent be responsible (just like you mentioned).

In Angular, you could just do:

<MyInputComponent
(validate)="validateInput($event)"
[isValid]="isInputValid">
</MyInputComponent>

On change, the input component would emit the change for the validateInput to run and the parent component will then let the input know if it's valid or not. :)