-
Notifications
You must be signed in to change notification settings - Fork 0
Fix remote config post #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,7 +6,7 @@ import 'package:flutter_news_app_web_dashboard_full_source_code/app/config/confi | |
import 'package:flutter_news_app_web_dashboard_full_source_code/bootstrap.dart'; | ||
|
||
// Define the current application environment (production/development/demo). | ||
const AppEnvironment appEnvironment = AppEnvironment.demo; | ||
const AppEnvironment appEnvironment = AppEnvironment.development; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hardcoding the application environment can be risky, as it might be accidentally merged and deployed to production. A more robust approach is to use compile-time variables with
|
||
|
||
@JS('removeSplashFromWeb') | ||
external void removeSplashFromWeb(); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For improved null safety and code clarity, it's best to avoid the null assertion operator (
!
). You can assignstate.originalRemoteConfig
to a local variable. After the null check, the compiler will know the local variable is not null, making the code safer and easier to read.