Support rendering node details extras #3244
Merged
Conversation
This file contains 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
…rNodeDetailsExtras function.
fbarl
changed the title
|
Could this table be implemented using the scope-details-data schema? I guess not completely, but it would be another interesting way to support client plugins/customization. If there was a way to fiddle w/ the details response structure and add on another table. Though perhaps more fragile if it was to change. Would have to document it better. |
@foot That's an interesting idea that might become more relevant in the future - feel free to open an issue! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #3243.
Not to be merged before https://github.com/weaveworks/service-ui/pull/2821.
Test like #3239.