-
Notifications
You must be signed in to change notification settings - Fork 83
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
Respect 'title' field when rendering object properties from json schema in helm charts #878
Comments
Hello, The screenshot you provided suggests that you might not be using the latest version of Onyxia. It seems that the most recent versions do support rendering the “title” property. Let me know if you need further assistance! |
We're running version |
Really sorry, I overinterpreted. I’ve made the fix and am waiting for @garronej feedback. Thank you for the report! |
Hello @skykanin thanks for reporting and @ddecrulle thanks for taking this so quickly. |
AFAICT the fix in 4bd9b0a only applies to root settings elements, but the 'title' field in non-root object properties should be respected too. In the example below the root This was tested on {
"resouces": {
"title": "Ressurser",
"description": "Velg minimum mengde RAM og CPU som skal være tilgjengelig i tjenesten.",
"type": "object",
"properties": {
"requests": {
"title": "Forespørsel", // This is not used during rendering
"description": "Velg mengden CPU-ressurser i millicores (M)",
"type": "object",
"properties": {
"cpu": {...},
"memory": {...}
}
}
}
}
} |
Hello @skykanin it should be fixed for good now. |
Currently object property names are rendered in the onyxia UI by capitalizing the json key. Instead read the corresponding 'title' field the same way it is done when rendering other data types in the form.
So a property like this in
values.schema.json
:should instead render with the name "Kildedata" and not "SourceData".
The text was updated successfully, but these errors were encountered: