Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: support for extra field in registry type (#2927)
<!-- Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes, and how it affects the users and other developers. --> ### This PR resolves [#2914](#2914) issue related Core PR: [#3208](lablup/backend.ai#3208) 24.09~24.09.2 : Using `container_registry_nodes` but does not support extra fields. 24.09.3 ~ : support extra field **Changes:** Extra field and argument are supported from version 24.09.3 onwards. Because the arguments for each mutation are not provided as input types, you must create a separate mutation if you want to exclude a specific argument. - Added `extra` field to container registry nodes to support additional JSON metadata - Added JSON editor UI component for managing extra information in container registry editor - Added validation for proper JSON formatting with error messages - Made `value` and `onChange` props optional in BAICodeEditor component - Added translations for JSON format validation messages across all languages **How to test:** 1. move to registry page 2. enter Extra Information to verify that the request succeeds only for valid JSON types. |dark|light| |---|---| |![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/lSyr8xXz1wdXALkJKzVx/2d12bdad-402f-4fdf-a3ca-f3a33c7839a2.png)|![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/lSyr8xXz1wdXALkJKzVx/1b44f9a6-384d-4f6d-9d3b-a51ed8b79e51.png)| **Checklist:** (if applicable) - [ ] Mention to the original issue - [ ] Documentation - [ ] Minium required manager version - [ ] Specific setting for review (eg., KB link, endpoint or how to setup) - [ ] Minimum requirements to check during review - [ ] Test case(s) to demonstrate the difference of before/after
- Loading branch information