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

fix: Add trigger message details documentation #1398

Merged
merged 1 commit into from
Oct 10, 2023
Merged

Conversation

doubleface
Copy link
Contributor

No description provided.

@doubleface
Copy link
Contributor Author

@Crash-- @paultranvan @Merkur39 Can I have a review for this please ?

@@ -75,6 +75,10 @@ import { QueryDefinition } from './queries/dsl'
* @property {String} type - type of the trigger. Can be "at", "cron", "event", "every", "in", "webhook", "client"
* @property {String} worker - type of worker. Can be "konnector" or "sendmail"
* @property {object} message - Parameters to pass to the the worker. For example, when the worker is set to konnector, message contains the related konnector and the related account.
* @property {String} [message.account] - Id of the account associated to this trigger, if any
* @property {String} [message.konnector] - Slug of the konnector associated to this trigger, if any
* @property {String} [message.folder_to_save] - Id of the destination folder of the konnector associated to this trigger, if any
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use something like this:

* @property {IOCozyAccount['id']} [message.account] - Id of the account associated to this trigger, if any
* @property {IOCozyKonnector['slug']} [message.konnector] - Slug of the konnector associated to this trigger, if any
* @property {IOCozyFolder['path']} [message.folder_to_save] - Id of the destination folder of the konnector associated to this trigger, if any

Like that, we add the "relation" between data.

Copy link
Contributor Author

@doubleface doubleface Oct 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I see.
I just fixed the message.folder_to_save attribute which is actually the id of the folder and not the path.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK cool 👍

@Crash--
Copy link
Contributor

Crash-- commented Oct 10, 2023

Last thing... If you tag a commit docs then we'll not publish a new version on npm.

Since you are editing the types and that types are used everywhere, you can tag it as a feat or fix as you want :)

@doubleface doubleface changed the title docs: Add trigger message details documentation fix: Add trigger message details documentation Oct 10, 2023
@doubleface doubleface merged commit 892a720 into master Oct 10, 2023
4 checks passed
@doubleface doubleface deleted the doc/TriggerMessage branch October 10, 2023 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants