Draft
Conversation
gvelez17
commented
Aug 9, 2023
| * http fetch timeout | ||
| */ | ||
| @jsonMember(Number, { name: 'http-fetch-timeout' }) | ||
| httpFetchTimeout?: number |
Contributor
Author
There was a problem hiding this comment.
i would like to use this in ./packages/common/src/utils/http-utils.ts but its not clear to me how to best do that - @stbrody would love thoughts on how to set up configuratble flags and feature flags more generally, is daemon config the right way to do it?
Contributor
Author
There was a problem hiding this comment.
@stephhuynh18 maybe you have an opinion?
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
1 participant
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.
Description
Include a summary of the change or link to the issue it addresses.
Include relevant motivation, context, brief description and impact of the change(s). List follow-up tasks here.
How Has This Been Tested?
Describe the tests that you ran to verify your changes. Provide instructions for reproduction.
PR checklist
Before submitting this PR, please make sure:
References:
Please list relevant documentation (e.g. tech specs, articles, related work etc.) relevant to this change, and note if the documentation has been updated.