feat: abstract postMessage

[JavierCane]

Purpose: Do not have to take into account from where to where you want to post messages

Current errors:

It seems to properly work because the use cases are executed properly, but it show errors like we would be performing memory accesses out of bounds :S

Just as a note, I have tried to refactor the abstracted method as follows, and the error changed to a table index out of bounds, so it could be something related to hoisting or whatever JS behaviour that changes depending on how we declare the function:

export const postMessage: <CommandType extends Command>(
  command: CommandType
) => void = () => {
  const isFromSceneSandboxToUiIframe = typeof window === "undefined";

  if (isFromSceneSandboxToUiIframe) {
    return function <CommandType extends Command>(command: CommandType): void {
      figma.ui.postMessage(command);
    };
  }

  return function <CommandType extends Command>(command: CommandType): void {
    window.parent.postMessage({ pluginMessage: command }, "*");
  };
};

[JavierCane]

It does seems that something is already buggy on the main branch. Same behaviour (the plugin executes successfully) but ends also with an error. In this case an error related with function signature mismatch :S

[JavierCane]

declaring it as a function has other behaviour:

export function postMessage(): <CommandType extends Command>(
  command: CommandType
) => void {
  const isFromSceneSandboxToUiIframe = typeof window === "undefined";

  if (isFromSceneSandboxToUiIframe) {
    return function <CommandType extends Command>(command: CommandType): void {
      figma.ui.postMessage(command);
    };
  }

  return function <CommandType extends Command>(command: CommandType): void {
    window.parent.postMessage({ pluginMessage: command }, "*");
  };
}

[JavierCane]

Tested out again in the main branch. It does not throw any error.

VIVA LA CACHE