Dotenv setup with environment selector & interceptors #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
agustinkoll-rootstrap
requested review from
amaury901130,
juanRodriguez17 and
tarruk
juanRodriguez17
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Introduces dotenv environment configuration with an example file (/env/.env.example).
Adds an Environment Selector on the login screen to switch APIs at runtime without rebuilding—flexibility to test multiple environments without creating a new build.
Configures Dio with logging and auth token interceptors. New auth header interceptor that injects the token header. And adds LogInterceptor in debug mode.
Cleans up the repository by removing files that shouldn’t be committed.
preferences.dart now include clear() to fully remove persisted credentials.
Issue
Preview
@rs-gpt-review Describe the changes in this PR. Recommend improvements (including code improvements), possible memory leaks, and best practices.