Implement GitLab Project Integration with Topics Management #247
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.
Description
This pull request implements a new Vue.js component for configuring GitLab integration settings. The component includes toggle switches for enabling/disabling the integration and including/excluding archived projects, as well as a list for managing topics. The settings are saved to the server using an API call when the user clicks the "Update" button. The component also fetches the current configuration from the server when it is created and populates the UI with the existing values.
Note
Depends on DependencyTrack/hyades-apiserver#1052
Addressed Issue
The addressed issue here is to implement a user interface for configuring GitLab integration settings. The settings include
enabling/disabling the integration, including/excluding archived projects, and managing topics
Additional Details
The code is written in Vue.js and utilizes the BootstrapVue library for styling. It consists of a card with two toggle switches for enabling/disabling the GitLab integration and including/excluding archived projects. A list of topics is displayed, with the ability to add, remove, and edit topics. The settings are saved to the server using an API call when the user clicks the "Update" button.
The code also handles fetching the current configuration from the server when the component is created, and populates the UI with the existing values.
Checklist