Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

Optional groups for SQL based destinations #3083

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

pauloouriques
Copy link
Contributor

@pauloouriques pauloouriques commented Mar 4, 2022

Change description

This PR contains the code to permit SQL based destinations to have optional groups.

Checklists

Development

  • Application changes have been tested appropriately

Impact

  • Code follows company security practices and guidelines
  • Security impact of change has been considered
  • Performance impact of change has been considered
  • Possible migration needs considered (model migrations, config migrations, etc.)

Please explain any security, performance, migration, or other impacts if relevant:

Code review

  • Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached where applicable.
  • Relevant tags have been added to the PR (bug, enhancement, internal, etc.)

@pauloouriques pauloouriques added enhancement New feature or request plugin labels Mar 4, 2022
Comment on lines +11 to +18
checkOptionsIntegrity(destinationOptions);
if (
!destinationOptions.groupsTable ||
!destinationOptions.groupForeignKey ||
!destinationOptions.groupColumnName
) {
newGroups = [];
}
Copy link
Member

Choose a reason for hiding this comment

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

I guess that works!
This will have the side-effect of deleting any previously-set groups you had saved in the table

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants