Spawned out of a discussion from Discord this PR adds support for the monaco-yaml package, which allows reading a JSON Schema offering type-hints for Docker Compose files
Steps to Test:
Have a Komodo Core environment which has different kinds of compose files (files on disk, UI defined, etc) along with arbitrary yaml files defined as sidecar configs
Navigate between different kinds of editors
Only docker compose file yaml files should have type hints from the plugin, others should be ignored.
There should be no regressions with the rest of the editors
Proof of Work:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/moghtech/komodo/pull/772
**Author:** [@chrishoage](https://github.com/chrishoage)
**Created:** 8/27/2025
**Status:** ✅ Merged
**Merged:** 8/27/2025
**Merged by:** [@mbecker20](https://github.com/mbecker20)
**Base:** `1.19.2` ← **Head:** `hoage/compose-schema`
---
### 📝 Commits (1)
- [`ed3c115`](https://github.com/moghtech/komodo/commit/ed3c115ad1c4e21bfeb3a65e771a9d617dd7e257) Add support for monaco-yaml and docker compose spec validatiaon
### 📊 Changes
**8 files changed** (+2018 additions, -4 deletions)
<details>
<summary>View changed files</summary>
📝 `frontend/package.json` (+1 -0)
➕ `frontend/public/schema/compose-spec.json` (+1900 -0)
📝 `frontend/src/components/monaco.tsx` (+3 -0)
📝 `frontend/src/components/resources/stack/config.tsx` (+1 -0)
📝 `frontend/src/components/resources/stack/info.tsx` (+1 -0)
📝 `frontend/src/monaco/index.ts` (+5 -1)
📝 `frontend/src/monaco/yaml.ts` (+16 -3)
📝 `frontend/yarn.lock` (+91 -0)
</details>
### ���� Description
Spawned out of a [discussion from Discord](https://discord.com/channels/1272479750065094760/1283197688292048949/1408907915125063700) this PR adds support for the [monaco-yaml](https://github.com/remcohaszing/monaco-yaml) package, which allows reading a JSON Schema offering type-hints for Docker Compose files
### Steps to Test:
1. Have a Komodo Core environment which has different kinds of compose files (files on disk, UI defined, etc) along with arbitrary yaml files defined as sidecar configs
2. Navigate between different kinds of editors
3. Only docker compose file yaml files should have type hints from the plugin, others should be ignored.
4. There should be no regressions with the rest of the editors
### Proof of Work:
<img width="1090" height="480" alt="image" src="https://github.com/user-attachments/assets/569cb42a-aedf-4954-9a4a-a2f394e8e70f" />
<img width="1234" height="407" alt="image" src="https://github.com/user-attachments/assets/2e3c884b-a274-4a92-a930-5b930bcc63a9" />
<img width="1425" height="530" alt="image" src="https://github.com/user-attachments/assets/04f37708-49e4-4bff-b320-d749ec5de8d8" />
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/moghtech/komodo/pull/772
Author: @chrishoage
Created: 8/27/2025
Status: ✅ Merged
Merged: 8/27/2025
Merged by: @mbecker20
Base:
1.19.2← Head:hoage/compose-schema📝 Commits (1)
ed3c115Add support for monaco-yaml and docker compose spec validatiaon📊 Changes
8 files changed (+2018 additions, -4 deletions)
View changed files
📝
frontend/package.json(+1 -0)➕
frontend/public/schema/compose-spec.json(+1900 -0)📝
frontend/src/components/monaco.tsx(+3 -0)📝
frontend/src/components/resources/stack/config.tsx(+1 -0)📝
frontend/src/components/resources/stack/info.tsx(+1 -0)📝
frontend/src/monaco/index.ts(+5 -1)📝
frontend/src/monaco/yaml.ts(+16 -3)📝
frontend/yarn.lock(+91 -0)���� Description
Spawned out of a discussion from Discord this PR adds support for the monaco-yaml package, which allows reading a JSON Schema offering type-hints for Docker Compose files
Steps to Test:
Proof of Work:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.