-
Notifications
You must be signed in to change notification settings - Fork 89
Put pubspec.lock under source control #87
Comments
@vicb : What could be possible solution for this. Kindly explain in detail as i am new to angular dart environment. |
@zoechi That issue was posted by me only :) |
@savantmohan there's probably a problem with version mismatch that comes form pubspec.lock not being versionned. This is what is requested by the linked issue. There's really nothing we can do in this repo for that. Edit: I thought I was posting in angular.dart..., here is the right place |
@savantmohan I know. I just wanted to connect them. |
Would it work to just change pubspec.yaml to have a specific version, rather than "any"? |
the .lock file has more versions (includes dependencies) so having the lock file versionned is really the best bet. |
@mhevery, @traceypowersg, @shailen: What's your opinion on putting the AngularDart tutorial's pubspec.lock under version control? At the very least, we should change pubspec.yaml to have a specific version of angular, but @vicb thinks that's not enough. |
@kwalrath this page has some useful information and the linked session states:
edit:
|
@vicb, I even wrote something about that (way back when): https://www.dartlang.org/tools/private-files.html#pubspeclock OK, you're right, we should check in pubspec.lock. And have someone responsible for updating it from time to time. |
Any volunteers? :) |
I would love to see angular adopting semver, see dart-archive/angular.dart#612 This way it would be easier to upgrade the lock files on BC breaks... But I guess pre-1.0 every single version might break BC. |
@kwalrath I think you should open a ticket. You'll probably be able to find a volunteer in the community. |
Fixed. Thanks, @vicb! |
As angular is moving really fast, users encounter issues trying the examples.
Versionning the lock file could help them by making sure that the dependencies are at a working version.
The text was updated successfully, but these errors were encountered: