Add standalone activity start delay to namespace capabilities#833
Merged
Conversation
spkane31
approved these changes
Jul 17, 2026
fretz12
commented
Jul 17, 2026
spkane31
force-pushed
the
fredtzeng/saa-delay-ns-cap
branch
from
July 17, 2026 22:13
ff29e33 to
0287e6e
Compare
THardy98
approved these changes
Jul 17, 2026
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
3 participants
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 changed?
Added the standalone_activity_start_delay field to NamespaceInfo.Capabilities.
Why?
Clients need to determine whether standalone activity start delay is effectively available for a namespace without relying on server-version checks. This lets UI clients hide start-delay controls when the feature is disabled by server configuration.