The majority of the products I worked on was/is B2B and they consisted of many (MANY) web forms. You know how this goes.

• You have to create the form model in the component (especially if you use reactive forms)
• Create the HTML elements
• Create the HTML elements
• ...
• Create the HTML elements

Those HTML elements more or less have a wrapper <div> element, a <label> tag, an <input> field, elements for error messages. This goes on and on. 

Who is our best friend for situations like this? ctrl+c & ctrl+v :) Yeah I know. I've been there.

Someone might say that this "best friend" helps us in many different cases. Here a bell rings. What do you do when you have to re-use the same code again and again? The answer is Abstraction. 
​
You know how to abstract your code in JS, in TS in C# and in many other languages. What about HTML though? Continue reading to find this out :) 

Developing an application in Angular CLI is really fun and fast due to its nature and the features it offers to developers.  One of the great features it has, is the ability to run your code using different variables. Similar to environmental variables that are distinguish per se. But what are the environment variables and what is the relation with the ionic?

Have you ever had the need two components to communicate each other? Of course you had!

I bet that when you hear components communication or components interaction, you automatically think of @input @output decorators. 

Say that we have two components, parent and child. You want the parent component to interpolate on its template a property from the child component. How can we do this?

1. Make use of @output decorator.
   When the child emits an event, the parent will handle this, take the event arguments, assign the value on a another variable, and finally use that variable on the template interpolation. You don't say that is a short way :)
   
   
2. Make use of @viewChild
   
   
3. Make use of exportAs

In this post we will try together to build a form consisted of different components and we will try various implementations to achieve the best architecture. The final pattern that we will implement is the smart dumb.

We will try 4 different approaches and soon I will create a 5th one which will use the exportAs. 
The post is quite long but it worth's diving in :)

Our form will have:

1. Wrapper component (smart)
2. Basic info component (dumb)
3. Address component (dumb)
4. Credit Cards component (dumb)

The protractor.conf.js file is meant to offer a configuration for our e2e tests. The default which come with each new angular-cli app is very good and works really well. We shouldn't extend it unless we expect more.

Although it works well on localhost, what about the CI server?

On this post I wont explain what kind of configuration you might need for your CI, but how to separate the configuration and how to use it

As web developers we have been developing web forms almost on every app. How many times have you spent time searching on google (or bing - no offense ) on finding solutions to pre-select an option on a select control while using angular? Yeah I know! Many times. And when you read the solution you are like "Ohh yess!"
Let's demystify this