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

Updates for 0.7 release #59

Merged
merged 12 commits into from
Jan 3, 2014
Merged

Updates for 0.7 release #59

merged 12 commits into from
Jan 3, 2014

Conversation

mattiasb
Copy link
Contributor

@mattiasb mattiasb commented Jan 3, 2014

  • Use the exact same jshintrc as Leaflet
  • Add karma testing and jshint to Gruntfile
  • Remove the submodules mess (and use npm dependencies instead
  • Update Leaflet dependency
  • Port the IE quirks over to the new leaflet-oldie-classes

Use the same jshintrc as Leaflet, and fix all errors.
Add myself to copyright notice and add a license field to package.json.
Add grunt-contrib-jshint task to grunt and add it to the default task.
Update README.md
Use node packages instead of git submodules for the developer
dependencies.
This means using the Leaflet npm module and not using leaflet-tilejson
anymore.
This patch, by incident, also fixes all examples to explicitly load the
zoomslider since it doesn't load automatically anymore since 0.6.2.
Remove jake (since we use grunt now) and uglify-js (since we don't use
that at all).
Commit 165d334 made the zoom control not load automatically
anymore. This commit updates the tests accordingly.
Use the grunt karma task instead of our own hand rolled one.
Update Leaflet to 0.7.1
Make a conditional check for console.log in test2.html
Leaflet 0.7.x doesn't use specific styles for IE anymore and also drops
support for IE6. This commits does the same for us.
Bump version to 0.7.0
mattiasb added a commit that referenced this pull request Jan 3, 2014
@mattiasb mattiasb merged commit 6520e14 into master Jan 3, 2014
@perliedman
Copy link
Contributor

Nice!

Using NPM instead of submodules is much cleaner.

@mattiasb mattiasb deleted the wip/0.7 branch January 3, 2014 12:33
@mattiasb
Copy link
Contributor Author

mattiasb commented Jan 3, 2014

Indeed. :)
And on that note, could you push 0.7.0 to npmjs? Or perhaps tell me how I can do it myself if that's possible.

@perliedman
Copy link
Contributor

Good idea. Do you have a npm user, and what is the username? (https://npmjs.org/doc/cli/npm-adduser.html otherwise)

@mattiasb
Copy link
Contributor Author

mattiasb commented Jan 3, 2014

mattiasb :)

@perliedman
Copy link
Contributor

Ok :) Added you as owner, so you should be able to publish in the future.

Also, I published 0.7.0.

@mattiasb
Copy link
Contributor Author

mattiasb commented Jan 3, 2014

Nice thanks!

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.

2 participants