closes #185

I'm not saying merge this actually, however this is how the naming conventions would play out here.

I've had mixed feelings about them for awhile but in general, like them.
I've just never been a big fan of long filenames which is why I'm not in love with whatever.component.ts vs. whatever.ts, however it does make things clear.
This becomes more idiomatic when you consider most conventions suggest placing files inside a folder called components such as shown here in this PR.
So when opening files and you see:
app/components/home/home.component.ts
vs.
app/home/home.ts

First, for large projects with more than 2-3 nested hierarchies, you would need a screen or IDE at least wide enough to show the long path and filename when you have multiple tabs open to discern the difference between 2 of the same named files in different folders, ie.:
app/component/home/home.component.ts
vs.
app/component/users/profile/home.component.ts
^ just an example but it can definitely happen ;)

But in the end, I digress. Whatever the community believes is universally great.

If this is the way to go, then by all means, merge 👍