rework: environment structure for more flexible value handling #90
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.
Proposed changes
At the moment, handling important environment values is clunky and lacks flexibility. While this is acceptable for internal testing, it is not a sustainable approach for the future of the project.
The goal of reworking the environment structure is to make it more flexible. This change comes with both pros and cons. In Flutter, there is no reliable way to securely store secrets at runtime, unlike in some other languages. This is not a flaw of the language itself, but a limitation we need to account for.
As a result, the environment file is not intended to store sensitive data. If critical or secret values are required, an alternative solution must be used.
The app now requires the following properties:
BACKEND_URLGENERATOR_URLGIT_BUG_URLGITHUB_SUGGESTION_URLThe new structure requires a small migration for local usage. Since these values are required at launch, they must be provided at compile time. The start script must be enhanced with:
Types of changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any ofthem, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.