Skip to content

chore: feature flag resiliency - #38

Merged
EDsCODE merged 3 commits into
masterfrom
resiliency
Feb 14, 2023
Merged

EDsCODE merged 3 commits into
masterfrom
resiliency

Conversation

@EDsCODE

@EDsCODE EDsCODE commented Feb 7, 2023

Copy link
Copy Markdown
Contributor

What does this PR do?

Where should the reviewer start?

How should this be manually tested?

Any background context you want to provide?

What are the relevant tickets?

Screenshots or screencasts (if UI/UX change)

Questions:

  • Does the docs need an update?
  • Are there any security concerns?
  • Do we need to update engineering / success?

@EDsCODE EDsCODE changed the title chore: resiliency chore: feature flag resiliency Feb 7, 2023
@EDsCODE
EDsCODE marked this pull request as ready for review February 7, 2023 16:17
@EDsCODE
EDsCODE requested review from liyiy and neilkakkar February 7, 2023 16:17
@liyiy

liyiy commented Feb 7, 2023

Copy link
Copy Markdown
Contributor

should we add tests for this? (asking for android too)

@EDsCODE

EDsCODE commented Feb 7, 2023

Copy link
Copy Markdown
Contributor Author

Good point, the no-replacement on error yes I would say so. For timeouts idts

NSLog(@"%@",json);
success(json);
NSInteger code = ((NSHTTPURLResponse *)response).statusCode;
if (code < 300) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can this be anything other than 200?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean based on what we send?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants