### Restrict past dates and times from date time now

[GarethStar]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature with doc update

What is the current behavior? (You can also link to an open issue here)
Does not disable the past times within the current day

What is the new behavior (if this is a feature change)?
Disables the past times within the current day

Does this PR introduce a breaking change?
No, its just a useful feature to filter

Please check if the PR fulfills these requirements

• This PR is against the develop branch. (Please do not submit PR's to the master branch)
• The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Other information:

[coveralls]

Coverage remained the same at 100.0% when pulling dd0e591 on garethstar:master into 65350d3 on dalelotts:develop.

[dalelotts]

Thanks for the PR! Can you help me understand the use case? Why is so much code necessary?

[coveralls]

Coverage remained the same at 100.0% when pulling 815efb3 on garethstar:master into 65350d3 on dalelotts:develop.

[GarethStar]

@dalelotts, I wanted to make it possible to disable all of today's times prior to now (I may add on offset) so that when the users of my app are selecting a call back time, there is no chance of them selecting past times.

At first I thought it would be a case of removing the midnight setter, however this then disabled the selection of the date. I managed to stop that bug only for 2 more to spawn from that. Then I kept finding bug after bug until the solution grew into this, a cleaner solution is more than welcome.

[dalelotts]

Why doesn't accepting $view as a parameter and adjust the "cut-off date" work for this use case?

[GarethStar]

@dalelotts i haven't tried that, i'll look into it on Monday, i'll let you know how it goes. Thanks

[GarethStar]

@dalelotts Cheers, using the view parameter works great

[coveralls]

Coverage remained the same at 100.0% when pulling ef64cf2 on garethstar:master into 65350d3 on dalelotts:develop.