Fix: Resolve code gen in Flutter version 3.27.1 #1814
Conversation
|
Realm welcomes all contributions! The only requirement we have is that, like many other projects, we need to have a Contributor License Agreement (CLA) in place before we can accept any external code. Our own CLA is a modified version of the Apache Software Foundation’s CLA. Our records show that CLA has not been signed by @haitr. Please submit your CLA electronically using our Google form so we can accept your submissions. After signing the CLA you can recheck this PR with a |
|
@cla-bot check |
|
The cla-bot has been summoned, and re-checked this pull request! |
|
This needs to be resolved |
There was a problem hiding this comment.
I think this can only be merged as a short-term fix - pinning the analyzer package like that can cause incompatibilities with other generators that may require different versions.
As far as I understand, the failure reported in #1813 is due to element3 being added to DartType - could we instead of pinning the analyzer, provide a noSuchMethod implementation that returns never? Or does this break in a different way?
|
@nirinchev Agreed. #1815 came up with the better implementation than mine. |
Problem
It fails to start due to incompatibility issues with updated versions of the
analyzerandsource_spanpackages.Solution
Pin the versions of
analyzerandsource_spanpackages.Changes
Updated
pubspec.yamlto fix package versions:analyzer: pinned to version 6.9.0source_span: pinned to version 1.8.0