Alexander Kirsch

The issue is that this treated as an error and it's extremely annoying to deal with.

Right, but when you updates to `classpath 'com.android.tools.build:gradle:3.2.0'` the error appears.

Same issue...

Yes, that's clear, but in this case, it forces me to use some other way of error handling in addition to this library.

I believe that some kind of warning or assert needs to be added to this lib to warn a developer about this and avoid crashes.

I‘m a new to the Flutter ecosystem as we all are :) Unfortunately it's hard for me to purpose some solution right away. I will look into this issue a...

Here is the relevant discussion, just for reference https://github.com/flutter/flutter/issues/12319

Looks like this is a quite complex problem to solve, I looked at [implementation of this feature in freezed library](https://github.com/rrousselGit/freezed/blob/a00d5ae49cc45826387a82a593da77a0a6ce313f/packages/freezed/lib/src/tools/type.dart#L20), it is able to handle some cases indeed, but not...

Do you have suggestions on how can we possibly inform the end user about it? Unfortunately, I'm out of idea here 🤷‍♂️.

I don't have a strong opinion on this, but I see it as a separate feature and would keep it as a status quo for now. Perhaps we could reconsider...