x-services parsing error

[lvillis]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

As shown in the figure below, the name set in x-services will become a1 when referenced in the service. At the same time, the parameters set by x-services are not displayed on the front end.

👟 Reproduction steps

Using x-services..

👀 Expected behavior

x-services parsed correctly.

😓 Actual Behavior

x-services parsed error.

Dockge Version

1.2.0

💻 Operating System and Arch

RockyLinux9.2

🌐 Browser

Google Chrome 119.0.6045.124

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[syko9000]

It must be the yaml parser being used... it supports Fragments as you can see the port number in the first case

But doesn't seem to support YAML merge types, or at least not fully.

Both work correctly as far as docker is concerned.

However, I named the fragment &ports and the parser/serializer renamed my fragment to &a1.

Edit: the json version of the parsed file still contains the << which is awkward but could be mitigated with a
this.ports ?? this["<<"].ports or the like but you'd have to do that for all possible fields 😞

[syko9000]

Apparently the parse and parseDocument functions can take a second argument of { merge: true }. That does collapse the << into the object above so that the UI can read it properly... but then it saves the document in its merged form and not it's fragmented form. So, no super easy solution.

[louislam]

Two way binding for this syntax is almost impossible.

I think the interactive editor should be disabled when this syntax is detected in the yaml file.