Adding Development ServerConfigType #798
Merged
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
development
server 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: ServerConfigType
to ourServerConfig
struct, and to ourEnvironmentType
enum. Since our debug tools are populated using this enum, it's automatically added to ourChange Environment
action sheet.π See
β Acceptance criteria
Change Environment
and selectDevelopment
. Verify that all requests are going to the expected endpoint using the console.