Hi, this code is supposed to be a sample of good architecture, but as I can understand using the 'part' is discouraged by the Dart team now. Except some cases with code generators.
Also, there is a lot of functions and variables outside of classes in the library namespace. It's quite confusing for a novice who will learn flutter by your code. Because it's quite an advanced technique, not covered in tutorials for beginners.
But this app is great overall! It covers a lot of real-life problems, unlike other simple examples. So it will be amazing if this game will be some reference to good architecture and good code.
So, do you plan to rewrite this app to current best practices?
Hi, this code is supposed to be a sample of good architecture, but as I can understand using the 'part' is discouraged by the Dart team now. Except some cases with code generators.
Also, there is a lot of functions and variables outside of classes in the library namespace. It's quite confusing for a novice who will learn flutter by your code. Because it's quite an advanced technique, not covered in tutorials for beginners.
But this app is great overall! It covers a lot of real-life problems, unlike other simple examples. So it will be amazing if this game will be some reference to good architecture and good code.
So, do you plan to rewrite this app to current best practices?