You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The .freezed.dart file generated seems to keep on oscillating between two "versions" when running dart run build_runner build --delete-conflicting-outputs. Sometimes I get a result, other times I get a different one, despite the lack of changes in the source file.
the freezed class for DetailedWallet stays unchanged.
Additional info ApiError is built in another flutter module/dependency. When running the build_runner for the module containing DetailedWallet, the freezed for ApiError is already built and imported (so the issue cannot be caused by the DetailedWallet freezed class being built before the ApiError one)
The text was updated successfully, but these errors were encountered:
I seem to also have this problem across different machines, my colleagues g files are slightly different, like using (as num).toInt() as opposed to my generated files which simply use as int
Describe the bug
The
.freezed.dart
file generated seems to keep on oscillating between two "versions" when runningdart run build_runner build --delete-conflicting-outputs
. Sometimes I get a result, other times I get a different one, despite the lack of changes in the source file.To Reproduce
The following are other freezed classes: DetailedWalletDto, SelectedNetwork, Pfp, ApiError. I will only include
ApiError
since it may be relevant.Expected behavior
the freezed class for DetailedWallet stays unchanged.
Additional info
ApiError
is built in another flutter module/dependency. When running the build_runner for the module containingDetailedWallet
, the freezed forApiError
is already built and imported (so the issue cannot be caused by the DetailedWallet freezed class being built before the ApiError one)The text was updated successfully, but these errors were encountered: