How to Make Forms in Angular REUSABLE (Advanced, 2023)

[@DecodedFrontend]

‎Advanced Angular Forms Course - Limited 10% Discount Applied 🚀 bit.ly/advanced-ng-forms-discounted 💁 Follow Me: Twitter - twitter.com/DecodedFrontend Instagram - instagram.com/decodedfrontend LinkedIn - www.linkedin.com/in/dmezhenskyi Support Channel - bit.ly/donate-to-decoded-frontend

[@meolivares06]

Is there any way to buy the course from Brasil? I have only brasillians real

[@DecodedFrontend]

@@meolivares06 hi :) of course you can. You can buy it as usually and your local currency will be automatically converted during the purchase to Euro with a current exchange rate.

[@alekai988]

Hi!! Your videos are great as always, for the last 2 weeks I been trying to buy one of your courses (Advance forms), but I cant buy it, my card is being declined every time, I dont know why if already bought one of your courses before and I dont think its a problem with my bank, Im always buying stuff from internet xd

[@NuclearDragonTwitch]

Can you help me please? I can't bind Custom Control to emitEvent: false; I use Custom Control, but i need to "correct" some of inputs. So when user input smth - i can alter it, with setValue(value, {emitEvent:false}). It works with normal forms, but with Custom Form Control i read that updateValueAndValidity used ignoring "emitEvent" option with Custom Control. So what to do, to make emitEvent: false work? Or what method use, to replace it?

[@aissa.bouguern]

High quality content! Angular community is lucky having you! Keep up the good work!

[@DecodedFrontend]

Thank you :) I happy to hear that my content helps

[@praecantat1o]

the best angular teacher in the whole youtube

[@DecodedFrontend]

Thank you so much! :)

[@ericaska]

Thanks!

[@DecodedFrontend]

Thank you so much for your support 🙏🏻

[@figureskatinglessons]

Дуже корисне відео, дякую, Дмитро! Дізнаюся багато нового із ваших відео, туторіали зрозумілі, актуальні, дуже подобається ваш канал!

[@amosisaila8416]

Best Angular youtuber. Congratulations on your channel. Keep going the great work!

[@DecodedFrontend]

Glad to hear that! Thank you so much:)

[@Masonc971]

Amazing video as always. I appreciate what you do and wouldn’t be where I am today without your help!

[@DecodedFrontend]

Thank you so much for your feedback 🙌

[@youtubevideo557]

Useful lesson!

[@jsmn3751]

so thankful for this awesome content ! greetings from Egypt

[@Nabulio85]

Once again, thank you very much for this excellent video. The explanations are precise and very well illustrated. You are the boss.

[@diglettt]

Ok, you're awesome. Not often people make me subscribe them, keep it up!

[@hollow_ego]

Since this video came out I used this approach in two projects and I really love it. One thing that is missing for pretty much all dynamic form videos, tutorials and courses is to be able to dynamically hide or show a control based on another ones value. If you happen to know a solid solution for that, please make a video or add it to your course. In your course you already have a section about creating a form based on a json, but no way of adding conditions for visibility. I found a working solution, but it relies on mutability. For those wondering: I'm using a signal to hold the config of the form which includes a visibility state as well as conditions on when to show certain fields. Then I'm building a form based on that condition using the approach from this video. That way we can keep markup and from group in sync. Then I'm listening to value changes on the form group and look for any controls that might need to be updated. I then set their visibility to either true or false. However, since my config can be deeply nested I'm extracting all controls, that dependent on a another one, into a computed signal. I use this as a base to find controls to check and modify.

[@DmitryEfimenko]

Good little dive into intervals - the ControlContainer, but honestly, it looks like you are on your way to reinvent the wheel - namely the template driven forms

[@DecodedFrontend]

Hi Dmitry, I am really glad to hear your opinion, thank you 🙌 indeed, the inspiration for self-registered form control models I found in Template-Driven forms :) I know that with TDF it would be even easier to reuse the controls since the control registration happens there automatically but sometimes we just have to stick with reactive forms.

[@davidgarciasantes]

Nice video, I will investigate this solution in more detail, thank you continue as well 💪

[@YDG]

Thanks for the great tutorial. I have been trying to do this cleanly for a long time ! Would be interesting to have some testing strategies for the subform component, as it needs to be part of a encapsulating formgroup to be functionnal.

[@vinaykadam3897]

Great video! It solved my split form issue. However, do you mind addressing the test case for this as well?

[@yukipuki2224]

best advanced angular tutorials on youtube, high quality content. You cover advanced concepts in an understandable way. i am absolutly grateful for your service to the community I will definitly buy the forms course ;)

I used to pass the form around to huge component hierarchies... I didn't know you could avoid it. I'll never struggle again, thanks so much!

[@calbofacundo8549]

Really thank you man! greatings from Argentina! have a nice day!

[@mrmariuszr]

Interesting approach, previously in such cases I used Control value accessor. I think this has one advantage, we can keep the model reference in the main form model

[@DecodedFrontend]

ControlValueAccessor might be also a valid approach. It depends on the use case. CVA is useful when you want to make a component bindable with FormControl/FormGroup models which eventually brings support of angular form features like validations, etc.

[@renkzk_dev]

You've got some of the best content on Angular, thank you

[@Aliakbaresmaeiliiii]

. I appreciate man< I have never ever saw teacher like you when i had see this video i become exited to tell you realy apprecite it of you

[@DecodedFrontend]

Thank you! I am happy to hear that my work is useful 😊

[@alexdisd5670]

NICE VIDEO, IT REALLY HELPED ME. THANK YOU!

[@DhavalLad-vj3fe]

You are awesome dude. Perfect solution. Thanks a lot!

[@mykhailodekhtiarenko6436]

Absolutely fantastic!!!

[@ЗахарЛевчук-ш5ю]

Хорош мужик. Є відос майже на кожну проблему з якою стикався в Ангулярі яку він ще глибоко пояснює.

[@DecodedFrontend]

Дякую, козаче 🙌🏻

[@gameofnoobgon7199]

Thank you. very useful content.

[@shyagam]

Beautiful solution. Well explained. Well done.

[@vOnez212]

Great content. Much appreciated!

[@pawe8713]

its quite hard to understand at first, because im using angular first time, only for my project and i dont consider myself front-end developer. But even though i can quite understand what you are doing. Your explaining REALLY makes a difference (for example Host directive, passing ControlContainer by provider).

[@ugochukwuumerie6378]

Thanks for the effort 😊

[@the-real-pawook]

Nice approach, thanks, will definitely use in our project! How do you deal with the fact that nested part is invisible when inspecting a form declaration in the parent component, do you usually check the template as well?

[@DecodedFrontend]

this is a good question. I think you should look always for some balance. For example, how much I will win if apply this technique for a simple login form? Well, probably not too much, right? It will bring too much magic to your forms. But maybe if it is a complex piece of logic that would require a lot of boilerplate, validation logic, etc. Then probably a bit of magic isn't so bad 😊 Also, you can use only part of the whole pattern (providing only ControlContainer) and keep separately form models and the view if you want/need.

[@danandreev6673]

Wow, great solution. Thank you very much!!

[@ihor-pidhornyi]

So funny, I was facing such problem yesterday, and was using 'dirty' method to solve the problem. It looks pretty awesome and I think this thing will become more popular because of your contribution :)

[@oleksandrvorovchenko8674]

Cool! Thank you!

[@obadaka3918]

Very nice approach. Thanks a lot😃

[@exodproduction]

brilliant! you've earned a subscriber 👌👌

[@betsegawlemmaamersho1638]

Thanks you for the video. Please make a video for creating inline-editing feature for angular material table

[@emrehizli4444]

I have bought the advanced course :D It seems amazing!!!

[@DecodedFrontend]

Thank you 🙏🏻 I excited to hear your feedback in the future 😉

[@Talk_Tech]

Great solution really helpful :)

[@DimanIvanov]

Great solution! Thanks a lot!

[@angelpellejero8764]

Thank you so much for this amazing video

[@DecodedFrontend]

You are welcome :)

[@akkonrad]

Thank you Dmytro, you're producing a really great and unique piece of content. Secondly, although I really like this approach in some cases, I wonder if it doesn't break the typed forms. What if I would like to have a multistep form (order) with items and addresses as separate form groups? I would like to know it upfront, validate everything etc. And with this approach the starting form group has only single field. I feel CVA would be a better choice. So my question - is there a way to use type in root component with the approach you demonstrated?

[@nanasarathi]

As usual... Superb... Thanks for sharing this...

[@eduardo.hernandez91]

Great content, best regards from Cuba.

[@ams1ams53]

It would be great to make a video about accessability. like how to change font-size for the whole application.

[@palyons4817]

Fair play. Really solid explanation.

[@Dragon-facts-d3j]

dude i loved ur accent!!!!!1 thanks a lot, and keep going.

[@sergfree5857]

Perfect. Thank you so much, my new friend!

[@abuzar-o9m]

High quality content!🔥

[@Szergej33]

This is so good, thanks for the video! creating a separate component that implements ControlValueAccessor and Validator stuff, just to containt an inner FormGroup and behave as a control also works the same, but this method is so much less painful. How does this work with typed form though, if a child component is registering the FormControls on the parent FormGroup directive, and it is all configured in the remplate? To me it seems the parent will not know about the existence of those controls, as far as typing goes - it will ofc work in runtime just as the video shows.

[@AntonioSantana-ll8il]

Excellent Video!!!!!!

[@andreiarpenti2589]

Thanks for the lesson, it is really cool. Is it possible to use the same approach without adding a new FormGroup, but add just one control to the parent FormControl?

[@ilyatelefus3647]

Hi Dmytro. Could you give an advice what are cases to use this approach and what are to implement custom form control?

[@DecodedFrontend]

Thanks for your question:) Custom Form Control (aka ControlValueAccessor) is needed when you want to make a regular component behave as a form control and support corresponding features like validation. The pattern from the video is good for extracting a normal form control into some wrapper for reusing purpose.

[@ilyatelefus3647]

Thank you 👍🏼

[@sinhue]

Amazing content bro great job … 🎊 🎉

[@sajjadahmad6436]

Very helpful thanks

[@andriituryk327]

It's a nice approach, but would probably have issues with using strictly typed forms

[@Emekaelo]

I'm curious about what issues it'll have

[@andriituryk327]

​@@Emekaelo Without declaring form controls in parent component you will face an error. Of cource you can make those controls optional, but it's not the best solution. If you want to make the child component strictly typed, it can be not that easy )

[@hellicobacterpillory6677]

Hi, Dimitro! Continuing the topic of reuse, would you be interested in releasing a video about route reuse strategy?

[@ericaska]

❤ Thank you. This is perfect.

[@vladimirv.443]

Interesting idea. What about a template-driven forms? Does this approach only work with reactive forms?

[@DecodedFrontend]

With template-driven forms, it should also work but for TDF you don't have to register formControl manuals because ngModel doesn't under the hood

[@aram5642]

Another cool video, or should I say: a missing part of Angular docs! I finally understood the resolution decorators Thanks!. Given that the main form model (in this case: AppComponent) is incomplete (the remaining fields are dispersed across other components), how is this going to work with strongly typed forms? Also, if I wanted to author a form AddressGroupComponent that is usable in both ReactiveForms and template driven forms - would I have to author two separate components? I think Angular forms got a bit neglected over time.

[@vako816]

Hey 👋🏻 Thanks for sharing. I just curious how does it work with typed forms? 🤔

[@Matzul98]

What is next and very challenging is when you have Form Array: 1. Edit mode - you have database data which needs to populate the child reactive form array. Or not if we are in Add mode. 2. Send additional data to child component. Ex: Form array object has select box which requires some database objects and also determine values of another control in that Form Array. In the end you have two @Input, the edit mode array from database and additonal values for select box, which need to communicate with parent form group. I don't know if I will find this in the course. Nevertheless, thank you! Best one yet!

[@MohammedAta-lp6et]

Thank you for your great content. what about if this form group name is a form array ?

[@anhquande]

another great video, Thanks

[@ОксанаШванченкова]

дуже круте відео! дякую :)

[@mahdiandalib186]

thx man, plz create a full web using angular with admin panel

[@khumozin]

I was wondering, how do we unit test this in jasmine?

[@yukipuki2224]

Excellent Video. I am interested on how you set values in the form form an observable stream?

[@segundonunes]

Fabulous video. Does this work for a stepwise form with angular router?

[@hassangolzari6694]

thanks for video 🌺

[@sebastiankvak7593]

Thanks for video. I found an interesting thing here, So if we have some async validators, after each on destroy of our control we will fire updateValueAndValidity under the hood, and make some request. Maybe you know some workaround for this?

[@hamidkadkhoda6966]

that's awesome, thank you.

[@JoseAngelesSoftware]

great content, thanks from nexico

[@bifty9]

Thank you for this great idea! I use it for loose coupled components (with routing) that work together as a generic form. But i have a problem to make the injection / parentContainer optional. So if i want to use the same component as a single form component or with a parent form. Any Optional( ) or something like deps: [[Optional, NgForm]] is not working (still get an null injection error...). Any tips how to fix that?

[@bifty9]

Ah, i got it working. I used the Optional syntax wrong. First trys was with deps: [[Optional, NgForm]] Second Try was with an @Optional before the Token. But correct syntax is this: useFactory: () => inject(ControlContainer, {skipSelf: true, optional:true}) Now it works, you only have to adjust the getter for the "parent" Container to use the local formGroup instead of the one from the parent if it not exists. Also adjust the templat to provide a parentFormgroup then. Good Day folks and thx, fopr sharing tips 🙌

[@el2511]

Such a great content! 😄

[@Maddi_97]

Hi, thank you for the video! Really good! But I have a question. How can I reset the complete Form in the Parent Component? Calling reset on the Parent Container set the forms added by the child to null?

[@DecodedFrontend]

Hey! Thanks for your question :) You reset the form the same way as for the regular one. This is because the formControl created by the child component will be eventually registered in the parent formGroup, so it means that if you reset the root formGroup then all child form controls will be reset to null (or initial values)

[@ArturKwiatkowski-u2u]

You have amazing skills both coding and teaching although I do not like the reactive way for handling forms. It seems that, when going reactive we're doing job that the framework should do for us.

[@neon_342]

Hello @DecodedFrontend, your advanced concepts videos are very helpful. Can you please create a tutorial on how to build a Realtime Video chat web app in Angular 14 using webrtc protocol.

[@gusrbaut]

Awesome!!!🚀

[@ricardotovar4597]

With that way, Control value accesor is not necessary?

[@Sauravhunny]

I was looking for the similar stuff and it really helped me. thanks Alot. also i am trying to write unit test cases for same standalone component and its throwing error on this saying "no provider for ControlContainer". Any idea how to fix that i created one mockClass but not working.

[@luisfbg3960]

Hi Dmytro, How do you overcome the famous "Expression Changed After Checked" console error, in case you use in you main form template expressions like: "form.valid", since you are changing your parent component from a child(when you add the control)??

[@halgaska]

We have a parent component with several child components, several of which are further nested, and it's ReactiveForm. Instead of implementing CVA for every child component, or using Inputs/Outputs, we are using FormGroupDirective. So into every child component, that is a part of the form, we inject the FormGroupDirective and add the control to the parent form. Have you seen this approach? I would like to double-check somewhere whether this approach is okay and not breaking good practices :D And what would be a better approach, FormGroupDirective or your in the video?

[@DownzJeaH]

my question is by adding the formControls inside of the child component, how would you give a type to the formGroup in parent? partial?

[@DecodedFrontend]

Thanks for you question. Unfortunately, strict typing is challenging here and can be added to the disadvantages of this pattern :(

[@22plowman]

is there a git link for the code? Fantastic tutorial btw

[@m.f.2015]

thanks 🌹

[@maiksousavital1671]

How would I set the control values when receiving data from server? How to access the main object from parent form in the child form? @input?

[@МихайлоХоданич-я8н]

Hello. Thank you for video. I have one question about this way to use form. What about typed of parent form? If we get value of parent form we know that we have additional key and value but typescript doesn’t know. Please correct me if i am wrong

[@pritpalsingh5927]

How are you able to do this, from where did you studied this , thanks for this

[@amirhosseinfaraji7594]

thanks for this video. sometimes I separate my formGroups into child components and I use output to emit child form group to parent component. do you have any idea regarding this approach?

[@Szergej33]

that is a valid apporoach for simple stuff, or even use the banana in a box with ngModel. Outputs don't really mix with ReactiveForms all that well though, the idea of the FormGroup and FormControl objects is they keep all the state of the forms, and track updates, validity, dirty and touched states, and all those changes can be listened to as observables. Using an output gets you the data that you can bind to whatever function/variable you like, but it does none of the logic of FormGroups. If you wanna split a FormGroup as a child component, you can implement the ControlValueAccessor interface on the component, and make the child FormGroup look like a single FormControl to the parent form, with the data defined in the same interface. Passing validators then becomes a bit tricky, so usually let the child form worry about the validation errors, and the parent only needs to be notified of validity, touched and dirty states.

[@canergurelsoy6875]

very nice, Thanks for sharing. But I've one question thou, how about creating a standalone component with sevral different html, how do use change this component html template dynamically?

[@hugofilipeseleiro]

Salut !! Very nice !!

[@ShubhamAkolkarx7]

Why is it important to remove control on onDestroy of shared form component?

[@blainefire4588]

thank you sir subscribed

[@Nikkvv]

Я недавно чуть не цілий день потратив. Знайшов інше рішення, але це виглядає набагато краще)

[@DecodedFrontend]

Дякую за коментар) яке було ваше рішення, якщо не секрет?)

[@Nikkvv]

constructor(private rootFormGroup: FormGroupDirective) {} ngOnInit(): void { this.form = this.rootFormGroup.control.get( this.formGroupName ) as FormGroup } Щось таке надибав😅@@DecodedFrontend

[@MsEntombed]

Thx for vide. I have question, how can we update the value of the forms? Use form.patchValue?

[@DecodedFrontend]

You are welcome. Yep, patchValue could be an option

[@paulovieira8065]

Is there a translation option on the course platform? My English is still very basic.

[@MsEntombed]

This solution work with FormArray? If it’s not difficult, show in the next video how this is implemented, thanks

[@lorenzoleonori7623]

Hi! Thanks you for share this amazing feature. I 've two questions. I use this approach to create reusable input field (text/email/number and so on), select, radio etc... The reside in separate file and pass in input [controlKey], to the inputFiled component ([formControlName]="controlKey") and the magic appear. So the question is, what do you think about my solution? It's overkill? There is a simple one solution? Can I ask you what you think about compare your solution with the FormGroupDirective for create reusable form?