Need a implementation of a custom pipe for workshop purposes

Module routes can and should be separated into their respective modules as a means of better demonstrating application modularization.

Includes time units list

depends on:
#28

Core functionality like http and auth services should be extracted into a core module and then imported into the root module. This promotes a cleaner codebase and also adds emphasis the the fact that these are common across the application and are not feature module specific.

YYYyyyaaaahhhh!! It's out, so let's upgrade 👍

Timesheet details, timeunits, and possible progress bar can all be separate components.

Example: New Timesheet date validators

If a custom validator on a form is failing, the form is still considered valid (form.valid == true) if the regular validators are all valid.

This:

4.545454545454546% completed

Is useless.

We currently only have parent to child, but use EventEmitter and add an example showing how to do it

Allows us to do some cool things, a la display actual Angular 2 components alongside Markdown (think: ComponentPlayground in the React world)

@mcacek

(I can probably do this; PR at some point in the future)

In the slides

Putting this in here to make @mrkelly happy. He's welcome to implement it as he sees fit.

Per @jondejong (roughly)

The timesheet details are all messed up and too complicated, nested subscribes, etc. etc.

These look ridiculous. Need to be placed at least off to the right.

Could be the progress bar?

#32

Angular 4.0.0 invisible-makeover is out and we should update.

We need a means of demonstrating lazy loading within this application. I'd rather not pollute this application with unnecessary functionality but we need to either include lazy loading in the application or find another way to demonstrate how this can be implemented. I am thinking that this is either code in the app or a slide?

Right now we have 2 node projects: The API and the the client. Merge these into one project with one unified set of dependencies and run scripts. This will be one less step to kick off workshops.

Via the index.ts, I believe we should be able to import from the auth package like this:
import {IdentityService, LocalStorage} from '../auth';

But that doesn't work. Instead we need to use this format:

import {IdentityService} from '../auth/identity.service';
import {LocalStorage} from '../auth/localStorage';

The API does authentication, but not authorization. No URL is actually protected by token access.

Timesheet details view should have a progress bar (like the implementation in Angular 1)

There is a lot of SASS copy and pasted that should be moved up in the component tree. Also that resulted in a lot of unused duplicate SASS that should be removed.

IntelliJ is telling me there semantic errors with login.service.ts. I can't figure out what's wrong with it. Usually in this case I eventually find out there the IDE is correct and there is something wrong with the code. But I'm a a loss. Extra eyes on this to make sure I'm not missing something would be nice.

ExtHttp currently has a hardcoded configuration which should be replaced with a provider configuration via CoreModule.forRoot. ExtHttp should not determining configuration based on its own inspection of the runtime environment and instead should be provided with that configuration.

Hi guys,

I am tryting to clone and install this repo and getting an error. Running on Windows 10 with Node 7.7.3 and npm 4.1.2. Tried on early versions as well and got same error.

** NG Live Development Server is running on http://localhost:4200. **
Hash: 128196aa548d9fc95a24
Time: 13335ms
chunk {0} main.bundle.js, main.bundle.js.map (main) 104 kB {2} [initial] [rendered]
chunk {1} styles.bundle.js, styles.bundle.js.map (styles) 30.6 kB {3} [initial] [rendered]
chunk {2} vendor.bundle.js, vendor.bundle.js.map (vendor) 4.55 MB [initial] [rendered]
chunk {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]

ERROR in Cannot read property 'provide' of null
webpack: Failed to compile.