Open nickolight opened 1 year ago
It could be a great idea to publish a new version for the v3 supporting analyzer
> 6.x.x
I'm currently using a fork that does just that because every other builders I use are compatible with analyzer 6.3.0
. This is really straight forward.
@ndelanou could you link said fork here? It would be of immense help; thanks
@sohaibbg Here you go: https://github.com/ndelanou/isar/tree/analyzer-v6
This would also address: https://github.com/isar/isar/issues/1468
I'd like to +1 this request, as currently I have to comment / uncomment isar_generator
and riverpod_lints
due to dependency conflict on analyzer.
just adding a comment here in case someone else is looking for a solution to this. it appears that using the following versions we won't need isar_generator
any longer, hence resolving the analyzer
dependency conflict:
isar: ^4.0.0-dev.14
isar_flutter_libs: ^4.0.0-dev.14
+1 to this request. Why is the dependency locked in below analyzer 6.0.0 in the first place? Wondering if changing it to ^6.0.0 would be safe like what @ndelanou did.
going to add on this reply: using v4.0 had its own limitation, namely android sdk version. so I ended up using dependency_overrides
and seems to be working without any issues:
dependency_overrides:
analyzer: ^6.0.0
with this in place I can have all of below working nicely together:
dependencies:
isar: ^3.1.0+1
isar_flutter_libs: ^3.1.0+1
dev_dependencies:
isar_generator: ^3.1.0+1
riverpod_lint: ^2.3.7
so I guess since isar_generator package has been removed from v4+
, the only viable solution until v4
is released is to use dependency_overrides
. and we could close this issue?
just adding a comment here in case someone else is looking for a solution to this. it appears that using the following versions we won't need
isar_generator
any longer, hence resolving theanalyzer
dependency conflict:isar: ^4.0.0-dev.14 isar_flutter_libs: ^4.0.0-dev.14
To summarize how to make it work: The analyzer definition must be overridden in the "_dependenciesoverrides" section (analyzer: ^6.0.0). To use analyzer version 6.3.0, you should also override the meta package:
dependency_overrides:
analyzer: ^6.3.0
meta: ^1.11.0
It's like an opportunity for developers to run a project and move on, but not a packaged solution or solution for that issue. That issue will be closed when package dependencies are updated!
"I also suggest making the change because I faced the same issue today...
Steps to Reproduce
Could you update the package dependencies? I want to use the latest version of the analyzer.
Code sample
Details