Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add: Disable date selection before now #92

Open
wants to merge 79 commits into
base: dev
Choose a base branch
from

Conversation

cbw-jmccormick
Copy link

We needed to disable the date selection if it was for a day in the past. Here is the code we wrote for it, let us now what you think.

g00fy- and others added 30 commits June 14, 2013 10:33
…equired)

removed console.logs
reformatted index.html
updated bower dependencies (angular-unstable)
updated README g00fy-#2
moved templates from `scripts` to `templates` directory
more verbose template names
updated `translate-z` to higher value - so we don't have conflicts with things like modals
unified bower.json with `master` branch
unified readme
updated `grunt` tasks to copy readme and bower.json
You can just as well use the relative version of input without loading jquery now.
don't require jquery in the 'relative' branch of a if/else in input
Makes it way more easier to maintain grunt plugin loading instead of matchdep.
chore(grunt): use load-grunt-tasks module
set321go and others added 27 commits June 29, 2014 13:59
as used in my mushin app
Add ngModel optional requirement for make ngChange Work, now just add ng-model and ng-change and be happy.
before we have a problem with the ngChange, the model does not change in the same time when the trigger callback, now it's ok.
using HTML entities rather than UTF-8 chars.
Date range datepickers always set to show correct dates when opened
Autoclose to popup calendar
@eralha
Copy link
Collaborator

eralha commented Apr 7, 2015

Can you rebase this PR? and make a plunker with this working?

@cbw-jmccormick
Copy link
Author

Looks like I was working on master, then pushed to dev (hence all the extra garbage). Would it be easier to close this pull request, and resend it so you only have the files we changed?

@eralha
Copy link
Collaborator

eralha commented Apr 9, 2015

Yes it would be easier to just have the files that changed, and be shure to update your fork, because some issues have been fixed since you PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.