Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(LoneScale Node): Add LoneScale node and Trigger node #5146

Merged
merged 9 commits into from
May 23, 2023

Conversation

SanYann
Copy link
Contributor

@SanYann SanYann commented Jan 12, 2023

Github issue / Community forum post (link here to close automatically):

@CLAassistant
Copy link

CLAassistant commented Jan 12, 2023

CLA assistant check
All committers have signed the CLA.

@n8n-assistant n8n-assistant bot added community Authored by a community member node/new Creation of an entirely new node labels Jan 12, 2023
@Joffcom
Copy link
Member

Joffcom commented Feb 9, 2023

Hey @SanYann,

I was just starting to review this and I got part of the way through it and I was wondering if this was finished or still a work in progress?

@Joffcom Joffcom changed the title feat(LoneScale Nodes): Add trigger node and manage lists node feat(LoneScale Node): Add trigger node and manage lists node Feb 9, 2023
@SanYann
Copy link
Contributor Author

SanYann commented Feb 9, 2023

Hey @SanYann,

I was just starting to review this and I got part of the way through it and I was wondering if this was finished or still a work in progress?

Hello, It is finished and tested locally

@Joffcom
Copy link
Member

Joffcom commented Feb 9, 2023

Hey @SanYann,

Perfect, I had to double check as there were some things that were a bit odd. It looks like the linter is still showing some errors and there is no support for continueOnFail. I have added in a credential test and moved all of the requests to use the same function.

When I was looking at the UI I noticed that adding a company and a contact uses the same fields, Is that expected? Looking at the API docs there might not be a first name field for company. Do you know if there is a way to get hold of test credentials or would signing up for a trial be the best bet?

@SanYann
Copy link
Contributor Author

SanYann commented Feb 14, 2023

Hey @SanYann,

Perfect, I had to double check as there were some things that were a bit odd. It looks like the linter is still showing some errors and there is no support for continueOnFail. I have added in a credential test and moved all of the requests to use the same function.

When I was looking at the UI I noticed that adding a company and a contact uses the same fields, Is that expected? Looking at the API docs there might not be a first name field for company. Do you know if there is a way to get hold of test credentials or would signing up for a trial be the best bet?

Hello,

Thanks a lot for your improvements.
Company and People uses the same fields for now, you can for exemple create a people attached to a company.
To test credentials, I can create a test account with default password on your email address, you will just have to create a new one on your first connection

@Joffcom
Copy link
Member

Joffcom commented Feb 14, 2023

Hey @SanYann,

That could work, There is still a bit more tidying up to do and support for features like continue on fail and paired items but I think another couple of sessions and it should be in a good place.

@SanYann
Copy link
Contributor Author

SanYann commented Feb 14, 2023

continueOnFail

Do you have documentation I could follow or example to implement continue on fail and paired items?

@SanYann SanYann closed this Feb 14, 2023
@SanYann SanYann reopened this Feb 14, 2023
@Joffcom
Copy link
Member

Joffcom commented Feb 14, 2023

Hey @SanYann,

PairedItems can be found here: https://docs.n8n.io/integrations/creating-nodes/build/reference/paired-items/

ContinueOnFail I can't see anything for but most nodes will have it at the bottom of the item loop, It will look something like this...

const executionData = this.helpers.constructExecutionMetaData(
					this.helpers.returnJsonArray(responseData),
					{ itemData: { item: i } },
				);
				returnData.push(...executionData);
			} catch (error) {
				if (this.continueOnFail()) {
					returnData.push({ error: error.message, json: {} });
					continue;
				}
				throw error;
			}
		}

If you use the newer declarative style this sort of thing is taken care of for you as well and it normally means you can build out a node fairly quickly as you don't need to worry about some of the more standard things but both styles are valid.

@codecov
Copy link

codecov bot commented Apr 21, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.02 ⚠️

Comparison is base (4219490) 27.69% compared to head (c3d6cf5) 27.67%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5146      +/-   ##
==========================================
- Coverage   27.69%   27.67%   -0.02%     
==========================================
  Files        2947     2952       +5     
  Lines      180861   180986     +125     
  Branches    19634    19660      +26     
==========================================
  Hits        50090    50090              
- Misses     130026   130151     +125     
  Partials      745      745              
Impacted Files Coverage Δ
...nodes-base/credentials/LoneScaleApi.credentials.ts 0.00% <0.00%> (ø)
...ges/nodes-base/nodes/LoneScale/GenericFunctions.ts 0.00% <0.00%> (ø)
...s/nodes-base/nodes/LoneScale/LoneScaleList.node.ts 0.00% <0.00%> (ø)
...odes-base/nodes/LoneScale/LoneScaleTrigger.node.ts 0.00% <0.00%> (ø)
packages/nodes-base/nodes/LoneScale/constants.ts 0.00% <0.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@Joffcom Joffcom changed the title feat(LoneScale Node): Add trigger node and manage lists node feat(LoneScale Node): Add LoneScale node and Trigger node May 23, 2023
@Joffcom Joffcom merged commit 4b85433 into n8n-io:master May 23, 2023
eyaljoyous pushed a commit to eyaljoyous/n8n that referenced this pull request May 23, 2023
* allow execution on  node 19,20,22

* fix(ERPNext Node): Fix issue with credential test and add frappe cloud url (n8n-io#6283)

* fix(editor): UI copy fix for Date & Time node (no-changelog) (n8n-io#6291)

* whether -> when

* lint fix

---------

Co-authored-by: Jonathan Bennetts <[email protected]>

* feat(RabbitMQ Node): Add mode for acknowledging and deleting from queue later in workflow (n8n-io#6225)

* Add later in workflow mode

* Add new operation

* Acknowledge message in next node

* Add response and emit for responsePromiseHook

* Remove double success message, close channel correctly

* Answser messages correctly

* Remove option from delete operation

* move operation name to camelCase

* Fix versioning

* To remove: add action item in v1

* Add notice for delete from queue

* Correctly only execute only the delete operation

* Refactor delete from queue operator and add return last items

---------

Co-authored-by: Marcus <[email protected]>

* feat: Add dangerouslyUseHTMLString where needed (no-changelog) (n8n-io#6292)

feat: add dangerouslyUseHTMLString where needed (no-changelog)

* fix(Wekan Node): Handle response correctly (n8n-io#6296)

Fix bug when response wasn't array

* Added procfile

* Added procfile

* redployed

* redployed

* redployed

* redployed

* redployed

* redployed

* dont start

* redployed

* redployed

* update version

* redployed

* redployed

* redployed

* redployed

* Revert "update version"

This reverts commit c249585.

* add heroku stack version

* delete

* add app.json setting heroku build stack

* update

* update vite

* update mem

* update PORT

* redployed

* fix(core): Optimize SharedWorkflow queries (n8n-io#6297)

* optimize SharedWorkflow queries

* fix int to string ids

* fix(Strapi Node): Strapi credentials notice (n8n-io#6289)

* fix(SSH Node): Private key field as password and credential test (n8n-io#6298)

* fix: Prevent removing manual executions when setting says to save (n8n-io#6300)

* fix: Initialize license in queue mode correctly (n8n-io#6301)

* feat(Ldap Node): Add LDAP node (n8n-io#4783)

* feat(LoneScale Node): Add LoneScale node and Trigger node (n8n-io#5146)

* feat: Add SSO SAML metadataUrl support and various improvements (n8n-io#6139)

* feat: add various sso improvements

* fix: remove test button assertion

* fix: fix type imports

* test: attempt fixing unit tests

* fix: changed to using useToast for error toasts

* Minor copy tweaks and swapped buttons position.

* fix locale ref

* align error with UI wording

* simplify saving ux

* fix pretty

* fix: update saml sso setting saving

* fix: undo try/catch changes when saving saml config

* metadata url tab selected at first

* chore: fix linting issue

* test: fix activation checkbox test

---------

Co-authored-by: Giulio Andreini <[email protected]>
Co-authored-by: Michael Auerswald <[email protected]>
Co-authored-by: Romain Minaud <[email protected]>

* fix(editor): Fix canvas loading when page gets restored from bfcache (n8n-io#6304)

* fix(editor): Fix canvas loading when page gets restored from bfcache

* Lint fix

* fix(editor): Link to log streaming doc from log streaming (no-changelog) (n8n-io#6303)

link to log streaming doc from log streaming

---------

Co-authored-by: Eyal Fishler <[email protected]>
Co-authored-by: Jon <[email protected]>
Co-authored-by: Deborah <[email protected]>
Co-authored-by: agobrech <[email protected]>
Co-authored-by: Marcus <[email protected]>
Co-authored-by: Alex Grozav <[email protected]>
Co-authored-by: Omri Attoun <[email protected]>
Co-authored-by: Michael Auerswald <[email protected]>
Co-authored-by: Michael Kret <[email protected]>
Co-authored-by: Omar Ajoue <[email protected]>
Co-authored-by: Yann ALEMAN <[email protected]>
Co-authored-by: Giulio Andreini <[email protected]>
Co-authored-by: Romain Minaud <[email protected]>
Co-authored-by: OlegIvaniv <[email protected]>
@janober
Copy link
Member

janober commented May 25, 2023

Got released with [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Authored by a community member node/new Creation of an entirely new node Released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants