There are a few small differences between the coding style used in production apps and the style Flutter DevRel uses in their samples. I just wanted to call out a couple here and ask that they be incorporated into Flutter module.
The DevRel team has a standard analysis_options setup that we use across samples. We'd like for this project to match.
We generally avoid using underscores to represent unused parameters. This is so that readers learning Flutter's APIs from the code can see what the purpose of the parameter is, even if it's unused in that particular instance. Right now I only see one parameter that's been done this way. Renaming that one to "context" can help readers understand that BlocProvider uses a context when creating its Bloc or Cubit at a particular spot in the tree.
It's possible there may be a few more as the project advances. I'll try to call them out as early as possible, and y'all should feel free to ask any questions you have.
There are a few small differences between the coding style used in production apps and the style Flutter DevRel uses in their samples. I just wanted to call out a couple here and ask that they be incorporated into Flutter module.
It's possible there may be a few more as the project advances. I'll try to call them out as early as possible, and y'all should feel free to ask any questions you have.