Continuing Javascript problems when using promises

When using promises in Javascript, the main seatable API objects become undefined.

The issue is still present on seatable.io as of today, and happens as soon as any Javascript is executed that does whatever with promises.

The simplest example to reproduce is:

await output.text('hello mario!');
await output.text('hello luigi!');

This will only print hello mario!, and throw an error for the second time output is referenced.

When communicating with outside web resources, being able to use promises for the fetch function is pretty important. I would appreciate if you could look into this.

Here is a previous forum post about it (containing a kind of clumsy workaround), I wanted to follow up testing on the latest version of seatable.

Hi Dragan, thanks for taking the time to follow up. We’ll look into it.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.