a pubspec rules a collection of files. as a whole, they all have to be safe or unsafe
but the things pulled in as deps can each be safe or unsafe
I wonder if there's an override.
lower bound of 2.11 or lower
watch the video for the command.
actually, yeah, just watch the video. :)
I am just trying to keep things as is (I don't think I have the time to walk 16 modules right now and update them all, and update their deps, etc). But I have 2.12.0 SDK installed on my system.
and yes, those should compile just fine
you just won’t get NNBD treatment… it’ll be like the old times.
I started to set lower boundaries but it's opening a rats nest :)
Haha!
Because every version of angel_orm_generator from git depends on angel_orm from hosted and airframes_aggregation_server depends on angel_orm from git, angel_orm_generator from git is forbidden.
So, because airframes_aggregation_server depends on angel_orm_generator from git, version solving failed.
Yeah, totally a chain of issues erupting.
Bummer.
it will act in pre 2.12 mode if the pubspec says so
no need to change the sdk
I don’t know if that would break the interpretation of new features thoough
I guess I could always try it and see. :)
and https://github.com/dart-lang/sdk/blob/master/docs/process/language-versions-and-experiments.md is interesting, but dated
It doesn't say if it honors that for
pub get too.
I rolled back to SDK 2.10.4 for the time being, just so I can keep moving forward on my project. But, I'll see about trying to push on this more later.
Right now getting that annoying complaint that one requires git but the other requires host
Because every version of angel_orm_postgres from git depends on angel_orm from path and airframes_aggregation_server depends on angel_orm from git, angel_orm_postgres from git is forbidden.
So, because airframes_aggregation_server depends on angel_orm_postgres from git, version solving failed.
@kevinelliott my fork basically locks the existing code to SDK below 2.12.0 and changed all the dependencies to local so that I can upgrade the libraries, figuring out the inter relationship between the modules and fixing failed test cases. With 2.12.0 release, can now change the SDK module by module to see if anything breaks and fix them along the way
@kevinelliott this will take some time to get through, as there are quite a few external libraries involved
Sorry for the lack of messages from me recently. This weekend, I want to start taking care of outstanding issues (and to start working on getting Thomas's fork pulled into the main repo).
Ideally, all packages can be updated to support the recent versions of the Dart SDK, as well as null-safety. I will also get to work on updating the documentation.
Before I start working at my new job, I want to make sure that existing apps will at least continue to work, and get ready to either transfer ownership to a new person, or close things down if nobody specifically wants to take it over
In my personal opinion, it may be best for Angel to gracefully close down, and instead, most Dart-on-the-server mindshare can focus on shelf and Aqueduct