Adding support for the V2.0 endpoint about meteor-microsoft HOT 3 OPEN

Hi @Bandit,

Since it's a different endpoint (and does not yet fully support all of Microsoft's APIs), I thought it merited becoming a distinct package. I have so far held off on submittingghobbs:microsoft to Atmosphere because I want to make sure I am happy with the API—particularly with a set of helper methods for working with Graph resources.

I do think v2.0 is the way to go when possible, but I believe it would break things for a lot of people to move q42:microsoft to the new endpoint, and it could be confusing to support two endpoints with a single package. What do you think?

from meteor-microsoft.

Fair points @gwhobbs - I must admit I haven't fully investigated the differences between the old and the new - just saw that it supported both types of accounts (why on earth are there two types of accounts on different systems?). I'm planning to give your code a go next week - was so glad to see someone had tackled this issue already, as I have no idea how to write an oAuth package. :)

Is it worth considering is renaming yours to :microsoft2 or something like that before submitting to Atmosphere, to signify it's the new version? Right now there are so many Microsoft packages, but the only way to tell if they're the new or the old is to look at the API URI in the code. :(

from meteor-microsoft.

@Bandit,

Good point! I went ahead and renamed the package. 

from meteor-microsoft.