analyzer version too low for compatibility with null-safe packages #197
Comments
|
@SebastienSCochet I did a null-safe migration of the LegacyV3 branch, not sure if that helps https://github.com/JamesMcIntosh/jaguar_orm/tree/legacyV3 It's not too far of what's actually in master, doesn't seem like much has changed since the V3 branch |
|
Hi, I tried to use your verson @SebastienSCochet, but I got a lot of problems with the generator, and I did my own implementation of null safety based on the next versions: Flutter: 1.22.6 If you know how to publish in the flutter package repository pub.dev or if you have some documentation to follow, please share it. If you want to use my implementation in your flutter projects, just change the references as this: Flutter: 2.2.3 |
|
@JamesMcIntosh Is not the same work, you have too many issues, and I insist that are in generator, your implementation finished the build process with errors. Did you test the generator? with relationships? That's why I did my own and I deleted extra files that doesn't nothing. I don't care if you don't want to consider it. BR |
|
Hi @isaacfi, @tejainece do you have any time to help get that PR merged back in? |
|
@isaacfi Why creating a new repo instead of forking this one? @JamesMcIntosh Sorry I created another PR, but was not able to make your code work... It looked simpler to start from @isaacfi work... @tejainece It would be awesome if you have some time to look and merge the pull requests or to do the null safe migration yourself |
|
Hi @dedeweb, I have one-to-many relationships in my project, the only that I need was change the creation of the related Beans. For example: I have a table named JobCategory that has one to many relationship with the table Job (One job category has many jobs). And this is the code of my model: For Job Category: And for Job: As you can see the relationship beans, are created as getter properties and this avoid the problem of the creation of the main beans when you run the generation. I created a new repo, because the legacyV3 doesnt work to me, because in this version is not posible to have a Foreign-Primary Key and I have some tables that got it. Then what I did is use the code downloaded by pub get of the version of jaguar-orm and change the code to make compatible with null-safe. And I'll review you pull request, but try to generate your model as mine, I'm sure that will work at all. BR. |
|
Sorry, but it didn't work for me, I always had a "mismatching association type"' exception In parser.dart line 97, you compare byHasMany with other.hasMany, but byHasMany is affected with foreign.byHasMany which should be nullable and is not. |
Everything is in the title
The text was updated successfully, but these errors were encountered: