AppColors has been scope only to the themeData Styling now is only possible via themeData
So all build should define (if needed)
@override Widget build(BuildContext context) {
final l10n = context.l10n;
final theme = Theme.of(context);
final style = theme.textTheme;
final colors = theme.colorScheme;
final bloc = context.read<BlocInQuestionBloc>(); // .read , .select, .watch; depending on the usecase.
... use colors.primary etc now instead of Appcolors.pimaryColor in your PR.
use bloc.add() instead of context.read().add();
Type of Change
[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
[ x] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[x ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[x ] 🗑️ Chore
Pre-launch Checklist
[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read and ran all relevant commands as specififed in the Running Tests section of the Contributor Guide.
fonkamloic
commented
1 year ago
AppColors has been scope only to the themeData Styling now is only possible via themeData So all build should define (if needed)
... use colors.primary etc now instead of Appcolors.pimaryColor in your PR. use bloc.add() instead of context.read().add();
Type of Change
Pre-launch Checklist
pubspec.yamlwith an appropriate new version according to the pub versioning philosophy,///).