Creating new layer got error

[xuhzs]

When creating a new layer in the keymap editor, got the following error.

TypeError

Cannot read properties of undefined (reading 'length')

  https://nickcoutsos.github.io/keymap-editor/LayerEditorTab.4717bdf4236ae8216252.js:1:42545
  https://nickcoutsos.github.io/keymap-editor/LayerEditorTab.4717bdf4236ae8216252.js:1:96145
  https://nickcoutsos.github.io/keymap-editor/vendors.fc7fc484474dee29ffb7.js:2:386308
  https://nickcoutsos.github.io/keymap-editor/LayerEditorTab.4717bdf4236ae8216252.js:1:96117
  https://nickcoutsos.github.io/keymap-editor/LayerEditorTab.4717bdf4236ae8216252.js:1:42511
  https://nickcoutsos.github.io/keymap-editor/react.0b7d83a58560e2038899.js:2:68802
  https://nickcoutsos.github.io/keymap-editor/react.0b7d83a58560e2038899.js:2:135844
  https://nickcoutsos.github.io/keymap-editor/LayerEditorTab.4717bdf4236ae8216252.js:1:42473
  https://nickcoutsos.github.io/keymap-editor/react.0b7d83a58560e2038899.js:2:62433
  https://nickcoutsos.github.io/keymap-editor/react.0b7d83a58560e2038899.js:2:119535

[xuhzs]

Also try copying the error by clicking on the clip board button only copies the string "undefined"

[nickcoutsos]

Could you share the keymap file its failing on?

[xuhzs]

This is my keymap file. https://github.com/Zhuph31/zmk-new_corne/blob/main/config/eyelash_corne.keymap

I have manually added the last layer (OTHER). Right now the same error can be recreated by switching to this layer in keymap editor and try using "quick &kp assignment".

[nickcoutsos]

Thanks for this! I'm going to need to do some digging but I'm a little beat right now. Hopefully I can give it some attention this week.

One thing I'm noticing is that it's running into trouble parsing your &lt customization (if you flip to the behaviors tab you'll see it thinks you're making a custom behavior with no label). If you delete that node (or remove the compatible and #binding-cells properties) it seems to handle things better.

[xuhzs]

Does this mean that this is an error with my keymap, or just a way to mitigate the issue with keymap editor for now?
Sorry I'm very new to ZMK and does not know much yet.

[nickcoutsos]

So the bottom line probably is that if it compiles without issue in its current state then that's just something I need to be able to handle robustly in the app.

The other consideration is that it's at least unexpected. When you're doing &lt { ... } you're overriding properties of the existing behavior using that identifier. As far as ZMK and Devicetree go I don't think its exactly a rule that you shouldn't change compatible or #binding-cells but if someone actually wanted to do that it'd make more sense to just create a new behavior.

Long story short (unless I discover anything else): removing those properties should solve your problem, but I should also make a (hopefully simple) change so that this doesn't break for others.