Nikolaj Kappler

I don't really have an opinion on which option I prefer, but everything is better than failing silently 😅 However, while error messages can point the user in the right...

I guess I slightly prefer my original proposal of keeping it camel-case but ignoring the case in addition to adding error messages, because I think it might be less work...

There's an octoprint plugin for this: https://plugins.octoprint.org/plugins/arc_welder/?utm_medium=announcements&utm_source=octoprint&utm_content=1.3.12 Would be nice if there would be an experimental setting in Cura that does this, so no post processing step is needed...

I have the same problem untfortunately. I would be willing to dig into this, however a starting point would be really nice to have

It looks like the issue is that the `dereference` function from `json-schema-ref-parser` doesn't supply any information about the original definitions. As a result, the `standaloneName` property on the AST is...

I previously worked around this by re-declaring the definitions in the extended schema and adding a reference for each interface. I now found a better workaround which is to set...

This also fixes an issue where some interfaces would disappear when adding a comment to them 😅

I prepared a fix (see links above). However, it depends on the pull request from json-schema-ref-parser (also linked above). Until the PR is submitted and a new version is released,...

Does the codesanbox work for you? All I get is a black screen and some error messages in the console.

Seems like codesandbox is working again... I've modified the example, to basically do the same thing I am doing in my codebase. The behaviour seems identical, however in the codesandbox,...