Conversation
milomg
force-pushed
the
signal-graph-5
branch
2 times, most recently
from
June 6, 2025 03:01
fad4d1e to
43db63d
Compare
hawkgs
reviewed
Jun 6, 2025
hawkgs
approved these changes
Jun 9, 2025
hawkgs
reviewed
Jun 9, 2025
add a new devtools field in SupportedApis to check if the getSignalGraphApi exists
Contributor
|
This PR was merged into the repository by commit fd2fca8. The changes were merged into the following branches: main |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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 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.
add a new devtools field in SupportedApis to check if the getSignalGraphApi exists
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
See #60478 for a more complete demo
By setting this API to unsupported, we can also hide the UI until it is more complete
Does this PR introduce a breaking change?
Other information