-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New Feature]: Health API JSON Schema Update: Add componentType, componentCategory, and description fields #479
Comments
A comment regarding
Only those components that have their |
@galenatjpl Any updates regarding this feature request and if it can be completed in 24.4? |
@anilnatha I'm not yet sure if we can complete this in 24.4, but I think it's probable. I just think there are some other larger higher priority tickets still in the kitchen currently |
agreed. |
defaults: |
|
@hargitayjpl We added comments above to indicate the default and new list of proposed values |
@anilnatha Thank you, I will make the above changes today and I will create a MC for testing later this week |
@anilnatha Every new MC will now include three additional fields in its health status response:
Below is a sample JSON file reflecting these changes:
Testing Information The UI Dashboard can be accessed here: For testing new features, you can install and utilize Unity-UI from this link: You can do this by updating the marketplace file to point to the correct Unity-UI version in the Unity Marketplace repository: |
@hargitayjpl This is great news! Thanks for working on getting this implemented. We'll get started on implementing the changes on our end in this sprint. |
Checked for duplicates
Yes.
Alternatives considered
No.
Related problems
The UI/UX team had originally designed the UI's navbar to have categories to help organize links in the navbar and make it easier for users to find what they are looking for.
In addition, we expect the health API to include services (e.g. APIs, etc.) that a user wouldn't typically navigate to in a browser. So, we would need to know which of those items returned by the health API endpoint are items that have a UI the user should access.
Here is an example screenshot of the originally proposed navbar design:
Describe the feature request
The UI/UX team would like to propose the addition of two new fields that when filled in, helps bucket components into meaningful categories in the UI's navbar and help inform us of what should be added to the navbar as a navigable item. The values set in this field should be restricted to a specific set of values and those listed below are to get the conversation started on what the values should be.
NOTE: PLEASE REVIEW THE PROPOSED VALUES BELOW WITH THE UI/UX TEAM, BEFORE PROCEEDING. THESE ARE JUST PROPOSALS AT THIS TIME. Primarily
componentType
should be reviewed here.componentCategory
values are probably okay.componentCategory
administration
,catalogs
,development
,infrastructure
,processing
componentType
api
,ui
Example:
@rtapella Please chime in on what I have posted above to ensure the accuracy of the request and fill in any missing details, and if we want to add/change the list of possible values for each of the fields.
The text was updated successfully, but these errors were encountered: