rework of seatable-n8n-node

[christophdb]

Complete rework of the SeaTable Node.

• Adding two new triggers and 10 new actions.
• Actions use now versioning
• cleaner code structure
• already published and tested as community node (n8n-nodes-seatable)

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Great PR! Please pay attention to the following items before merging:

Files matching packages/**:

• If fixing bug, added test to cover scenario.
• If addressing forum or Github issue, added link to description.

Files matching packages/**/*.ts:

• Added unit tests to cover new or updated functionality.

Files matching packages/nodes-base/nodes/**:

• Added workflow tests for nodes if possible.

Make sure to check off this list before asking for review.

[christophdb]

Bump this Merge Request. Is there anything I can do to support the review of this PR?

[MehrCurry]

I wonder why this important change is delayed that long. As a user of n8n cloud i am waiting for the change. The community module is not an option for us cloud users.

[janober]

What is still outstanding @Joffcom ?

[Joffcom]

I will need to run through it again but I think it was a bunch of lint issues that I wasn’t able to push changes for.

[MehrCurry]

I tried the seatable community module on a self-hosted instance with docker on my machine. Exactly what i need. So this means i must switch from the n8n cloud solution to a self-hosted instance to get seatable usable. I was using a workaround with a scheduled trigger but that quickly exceeds the limit of my cloud subscription.

[Joffcom]

Hey @MehrCurry,

Sadly for now that would be the case as we have to ensure any PR follows our code standards before accepting it.

[MehrCurry]

Hey @MehrCurry,

Sadly for now that would be the case as we have to ensure any PR follows our code standards before accepting it.

I am working as a senior software architect and i would not recommend lowering the coding standards. But its sad to see this branch dying which already contains important enhancements. I love using n8n and i also like using Seatable but the current status makes them more or less unusable together.

Anyway thanks for your help.

[Joffcom]

Hey @MehrCurry,

We will get this sorted, I have blocked out some time next week to see if I can push to this branch again to go through the lint issues.

[MehrCurry]

Hey @Joffcom,

i am really glad and exited to hear that. I very much appreciate your work. Keep going.

Regards
Guido