Get ready for Leaflet 1.0

[nmccready]

From @simison on July 15, 2015 11:24

http://leafletjs.com/2015/07/15/leaflet-1.0-beta1-released.html

The release sports a number of minor breaking API changes, and some of the plugins will have to be updated. To make the upgrade less painful, we’re doing a short beta cycle before the final 1.0 to allow users and plugin developers to catch up to the changes while we find and fix remaining issues.

:-)

Copied from original issue: tombatossals/angular-leaflet-directive#851

[nmccready]

From @tombatossals on July 15, 2015 13:54

Wow, great news. That would be a good moment for giving this directive a power up.

Thanks for reporting!

[nmccready]

From @paambaati on August 4, 2015 4:56

@tombatossals Is there a branch for this that we could check out/test/contribute?

[nmccready]

Referencing Mobile Draw Support . IE: This is another reason to get started on this.
Wildhoney/Leaflet.FreeDraw#3

[nmccready]

I will be adding a leaflet 1.0.X branch to start working towards this. However I am not sure what the name of the branch should be.

leaflet-1.0.X to targets leaflet? Or just 1.0.X as we are working towards a 1.0.X ourselves.

My only beef with making it 1.0.X is that going to leaflet 1.0.X might not be stable right away. But keeping the branch with 1.0.X and mapping to leaflet 1.0.X helps eliminate confusion.

Thoughts anyone?

[nmccready]

From @vrubert on September 23, 2015 16:54

Looks good @nmccready, I think too we need that branch because it will need some time to have the directive working with leaflet 1.0.x and all the modules.

BTW, the Leaflet.FreeDraw project is amazing!!

[nmccready]

@vrubert @tombatossals any thoughts on what you want the branch name to be?

[nmccready]

From @simison on September 24, 2015 10:31

Keeping the future version number of this package at the branch name makes more sense to me rather than following Leaflet versions. Trying to follow Leaflet versions and keeping them in pair with package, might prove hard in long term, doable only maybe for major versions.

I'd call it "1.0.0-with-leaflet-1.x", "1.0.0-WIP" or just "1.0.0"

[nmccready]

From @tombatossals on September 24, 2015 17:56

Hey, I would suggest "1.0.0-wip" as @simison said, what do you think?

I haven't had time to take a look at leaflet-1.0-beta, I expect there will be no major API changes and 90% will work seamlessly. I hope so.

[nmccready]

Awesome I hope so too, what is WIP? Work In Progress? I am not sure if that is needed as all branches are WIP 😀 .

[nmccready]

Or is it WLP?

[nmccready]

hmm maybe just leaflet-1.X

[nmccready]

That way if we have any major changes (unseen foreseeable) we don't need to rename the branch.