Merged
Conversation
justinswart
approved these changes
Aug 14, 2019
Contributor
justinswart
left a comment
There was a problem hiding this comment.
Nice, thanks for adding that!
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📲 What
Adds a new
developmentserver config type, which uses our new team environment so we can test backend features without deploying to production or staging.🤔 Why
Previously, we could only test backend changes locally or on staging or production. Since our staging environment is a mirror image of production, and not technically an environment for active development, it was difficult for native clients to test WIP backend features.
With our new native team backend environment we can deploy WIP backend features and test them on the native clients using the debug tools.
🛠 How
Adds a new
development: ServerConfigTypeto ourServerConfigstruct, and to ourEnvironmentTypeenum. Since our debug tools are populated using this enum, it's automatically added to ourChange Environmentaction sheet.👀 See
✅ Acceptance criteria
Change Environmentand selectDevelopment. Verify that all requests are going to the expected endpoint using the console.