Cherry-picked fix from upstream commit 5ede340 #650
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
- Added component to handle missing environment variables. - Updated to check for and display if not set. - Updated to clarify that frontend env variables use and must start with . - Modified , changing to .
…variables example
feat: add BackendURL component and improve env variable handling
Add backend message loading to Home component and update environment …
Added autopep8 and prettier to template.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
As part of Case Study 5, I cherry-picked commit 5ede340 from upstream. However, the commit already exists in upstream/main, so Git showed "empty cherry-pick". I still created this PR to demonstrate the process.