Layout messages are forwarded with the wrong payload key in ApiProvider

[SxxAq]

I verified a runtime mismatch in the frontend layout message flow.

In js/api/ApiProvider.js, layout messages are forwarded as:

apiHandlers.current.onLayoutMessage({
  cmd: cmd.data,
  update: cmd.commmand == 'layout_update',
});

But in js/main.js, the handler expects:

const onLayoutMessage = ({ data, update }) => {
  if (update) parseLayoutsFromServer(data);
  else relayout();
};

So ApiProvider sends a cmd field, while onLayoutMessage expects data.

Verified runtime behavior

With temporary console logging added, I observed:

layout message from socket {command: 'layout_update', data: ''}
onLayoutMessage payload {data: undefined, update: false}

and also:

layout message from socket {command: 'layout'}
onLayoutMessage payload {data: undefined, update: false}

This confirms that the payload reaching onLayoutMessage does not match what the handler expects.

Expected behavior

The layout payload should be forwarded under the key that onLayoutMessage destructures, so parseLayoutsFromServer(...) receives the actual layout data.

Possible fix

Either:

• send { data: cmd.data, update: ... } from ApiProvider, or
• change onLayoutMessage to destructure { cmd, update }

[Nikita2106-05]

Thanks for pointing this out! I was able to reproduce the issue and found that the layout message payload from ApiProvider uses cmd while the handler expects data, which results in data being undefined at runtime.

I’ll fix this by aligning the payload structure and also address the commmand typo. Preparing a patch now.