From 59a87c9149de236f454b3d53e41b52bbc60a09e3 Mon Sep 17 00:00:00 2001 From: Rogerio Angeliski Date: Wed, 30 Nov 2022 16:26:18 +0000 Subject: [PATCH] docs: add useful information to custom transformers Signed-off-by: Rogerio Angeliski --- docs/integrations/github/org.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/integrations/github/org.md b/docs/integrations/github/org.md index c2e67843e9..234004073a 100644 --- a/docs/integrations/github/org.md +++ b/docs/integrations/github/org.md @@ -165,6 +165,10 @@ There is also a `defaultUserTransformer` and `defaultOrganizationTeamTransformer You could use these and simply decorate the response from the default transformation if you only need to change a few properties. +**Attention:** +When you use the Events Support with a `TeamTransformer`, you need to ensure your entity will have the +annotation `github.com/node-id` with the value from `team.id`. Without this, the `team.edit` event could fail to update + ### Resolving GitHub users via organization email When you authenticate users you should resolve them to an entity within the