feat(uptime): Send timeoutMs value as hidden field #78782
Merged
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
github-actions
bot
added
the
Scope: Frontend
michellewzhang
approved these changes
Oct 8, 2024
We'll need to start sending this, even though the backend won't yet accept it, so that when we do add timeoutMs to the backend APIs there's no backwards compatibility issues.
evanpurkhiser
force-pushed
the
evanpurkhiser/feat-uptime-send-timeoutms-value-as-hidden-field
branch
from
030f5bd to
e5d1331
Compare
evanpurkhiser
deleted the
evanpurkhiser/feat-uptime-send-timeoutms-value-as-hidden-field
branch
evanpurkhiser
added a commit
that referenced
this pull request
Oct 15, 2024
cmanallen
pushed a commit
that referenced
this pull request
Oct 23, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We'll need to start sending this, even though the backend won't yet
accept it, so that when we do add timeoutMs to the backend APIs there's
no backwards compatibility issues.