feat(#2002): Align adapter registration with other pipeline elements #2008
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
java
bossenti
approved these changes
Oct 16, 2023
…ation-of-adapters-and-pipeline-elements # Conflicts: # ui/src/app/add/components/endpoint-item/endpoint-item.component.ts # ui/src/app/connect/components/existing-adapters/existing-adapters.component.ts # ui/src/scss/sp/main.scss
bossenti
deleted the
2002-harmonize-registration-of-adapters-and-pipeline-elements
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Modify the registration process of adapters. Previously, adapters registered independent from other extensions like pipeline lements and couldn't be installed or deleted from the
Install Pipeline Elementsview.This PR harmonizes the behaviour and also stores assets of adapters (icons and documentation).
Remarks
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no