Update pubspec Intl version

[alan-knight]

No description provided.

[alan-knight]

@jbdeboer @mhevery Can you guys take a look at this? It's a problem for being able to use updated Intl versions, which have some important fixes. Note that one of the tests has to change because it relies on CLDR data that's changed.

[mhevery]

Please squash the SHAs together and follow our commit message guidelines: https://github.com/angular/angular.dart/blob/master/CONTRIBUTING.md#commit Than the PR should be ready to merge.

[vicb]

I have a question about this PR, we now have

intl: '>=0.8.7 <0.12.0' which means to the code is supposed to work with all those version.

The updated test obviously does not with 0.10 (because it needed to be updated). While this is not a big deal here, what would be the best way to handle this in general ? Should we not allow versions to span over BC breaks (intl: '>=0.11.0 <0.12.0') ?

Once again this is not a problem here, just thinking about general case.

[alan-knight]

It's a good point. I think the general rule is that the version shouldn't only span over BC breaks if the breaking change doesn't affect the way this package uses it. For example, a breaking change in Intl's message handling doesn't affect Angular, since it doesn't use it, but a change to date formatting does. Possibly a better fix for the test would be to change it to test a locale whose data didn't change between the two versions of CLDR and then it should work with all versions.

[alan-knight]

Squashed and fixed commit message.

[vicb]

@alan-knight for some reason I'm stuck with intl 0.8.10+4 (0.11.3 available) even after a pub upgrade (with your modifs). I can't figure out why I can not get a newer version, any idea ? (pub deps does not help).
If a set the req to intl: '>=0.11.0 <0.12.0' then 0.11.3 is used.
Isn't pub upgrade supposed to get the highest possible version, is this a dartbug.com ?

[alan-knight]

I think this is probably because of the thing Bob Nystrom was talking about
in the mailing list with analyzer dependencies. I'll broaden the dependency
in Intl and that might help some.

On Wed, Jul 30, 2014 at 1:35 AM, Victor Berchet [email protected]
wrote:

@alan-knight https://github.com/alan-knight for some reason I'm stuck
with intl 0.8.10+4 (0.11.3 available) even after a pub upgrade (with your
modifs). I can't figure out why I can not get a newer version, any idea ? (pub
deps does not help).
If a set the req to intl: '>=0.11.0 <0.12.0' then 0.11.3 is used.
Isn't pub upgrade supposed to get the highest possible version, is this a
dartbug.com ?

—
Reply to this email directly or view it on GitHub
#1203 (comment).

[alan-knight]

I published an updated Intl that allows current analyzer. I'm not sure if that will help your case or not. If I do a pub upgrade on angular it gets the current version of Intl.

[vicb]

@alan-knight great, thanks !