console
console copied to clipboard
x-descriptor for map and boolean pointer (UI Markers)
Is there any x-descriptor to show the maps in the UI and boolean pointer as switch? Existing text and other descriptor doesn't seem to work. The ALM annotations have the map field but it is not getting rendered in the UI
cc @tlwu2013 @TheRealJon
Hi, Any update regarding the issue of x-descriptors.
For the boolean switch, does this work for you?
https://github.com/openshift/console/blob/master/frontend/packages/operator-lifecycle-manager/src/components/descriptors/reference/reference.md#4-booleanswitch
I don't believe there is a way to show maps, so that would be a new enhancement.
Boolean switch seems to work for bool variables. However, pointers to data types like bool and string don't seem to work in similar fashion. ex. boolean switch doesn't show the desired output for *bool.
Console deals with the resource JSON, which doesn't have pointers. I'm assuming if the pointer is nil the JSON property is left out, and this breaks the switch? Or is it another problem?
This behaviour is also seen in case of string pointers which are being properly populated. So I'm assuming, we have to pass values explicitly?
There is a map field - Labels which gets rendered in the UI by default. How is this done?
Maybe we can leverage this to print other map structures?

Hi, @Milind21. I'm a little confused because JSON and YAML don't have the concept of pointers. Are you using a Golang API?
Yes, we are using golang and we had variables of type pointer which is now getting rendered. However, can you please open enhancement for map issue or let me know how to open that issue
HI, @spadgett, Can you please tell about the roadmap on when we might have support for rendering map on the UI.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.