- LOW COMPLEXITY - GTS Specification repository:
- create gts-spec/examples/typespec/vms folder and create several examples there - base VM type (CPU, RAM, name, ID), derived VM types for VMWare, Nutanix, Virtuozzo
- create gts-spec/examples/yaml/ui folder and create several examples there - base UI item and derived types menu item, grid, and instance - ui_item
menu_itemmy_menu_item
- update gts-spec/README.md and mention YAML and TypeSpec support and examples
- LOW COMPLEXITY - gts-python :
- add yaml support
- add typespec support
in the code, rename JsonFile -> GtsFile, JsonEntity -> GtsEntity, JsonPathResolver -> GtsPathResolver, etc.
I'd suggest to make a tiny fix to just remap yaml and typespec on read to JSON/JSONSchema, the rest logic should remain the same
- LOW COMPLEXITY - gts-kit:
- add yaml support in the parser
- add typespec support in the parser
- HIGH COMPLEXITY - gts-kit:
- add yaml support in the viewer (where we have JSON raw view)
- add typespec support in the viewer (where we have JSON raw view)
menu_itemmy_menu_itemin the code, rename JsonFile -> GtsFile, JsonEntity -> GtsEntity, JsonPathResolver -> GtsPathResolver, etc.
I'd suggest to make a tiny fix to just remap yaml and typespec on read to JSON/JSONSchema, the rest logic should remain the same