Skip to content

Commit c4a773d

Browse files
richardtreierrichardtreier
committed
sovity/edc-ui at v4.1.8 moved into /connector-ui (#1116)
2 parents 9dc5fb6 + 152abed commit c4a773d

File tree

494 files changed

+53671
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

494 files changed

+53671
-0
lines changed

‎connector-ui/.browserslistrc

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# This file is used by the build system to adjust CSS and JS output to support the specified browsers below.
2+
# For additional information regarding the format and rule options, please see:
3+
# https://github.com/browserslist/browserslist#queries
4+
5+
# For the full list of supported browsers by the Angular framework, please see:
6+
# https://angular.io/guide/browser-support
7+
8+
# You can see what browsers were selected by your queries by running:
9+
# npx browserslist
10+
11+
last 1 Chrome version
12+
last 1 Firefox version
13+
last 2 Edge major versions
14+
last 2 Safari major versions
15+
last 2 iOS major versions
16+
Firefox ESR
17+
not IE 11 # Angular supports IE 11 only as an opt-in. To opt-in, remove the 'not' prefix on this line.

‎connector-ui/.dockerignore

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
.idea
2+
.vscode
3+
misc
4+
openapi
5+
tmp
6+
node_modules
7+
src/assets/config/*.json
8+
.env*

‎connector-ui/.editorconfig

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# Editor configuration, see https://editorconfig.org
2+
root = true
3+
4+
[*]
5+
charset = utf-8
6+
indent_style = space
7+
indent_size = 2
8+
insert_final_newline = true
9+
trim_trailing_whitespace = true
10+
end_of_line = lf
11+
12+
[*.ts]
13+
quote_type = single
14+
15+
[*.md]
16+
max_line_length = off
17+
trim_trailing_whitespace = false

‎connector-ui/.env.local-dev

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# .env file configured for default npm run start commands
2+
# see app-config-properties.ts for list of all configurable values
3+
EDC_UI_ACTIVE_PROFILE=sovity-open-source
4+
5+
EDC_UI_USE_FAKE_BACKEND=true
6+
EDC_UI_MANAGEMENT_API_URL=http://edc.fake-backend
7+
EDC_UI_MANAGEMENT_API_KEY=no-api-key-required-in-local-dev
8+
EDC_UI_CATALOG_URLS=http://existing-other-connector/api/dsp,http://does-not-exist-but-is-super-long-so-we-can-test/api/dsp, http://how-wrapping-works-in-subtext-of-catalog-url-select/api/dsp
9+
EDC_UI_LOGOUT_URL=https://example.com/logout
10+
EDC_UI_CONNECTOR_ENDPOINT=http://localhost:3000/api/dsp
11+
EDC_UI_MANAGEMENT_API_URL_SHOWN_IN_DASHBOARD=http://localhost:3000/api/control/management

‎connector-ui/.github/ISSUE_TEMPLATE/bug_report.yaml

+62
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
name: Bug Report Template
2+
description: Report a bug to help us improve
3+
labels: ["kind/bug"]
4+
body:
5+
- type: textarea
6+
id: description
7+
attributes:
8+
label: Description - What happened? *
9+
description: A clear and concise description of the bug.
10+
placeholder: Tell us what you see!
11+
validations:
12+
required: true
13+
- type: textarea
14+
id: expected
15+
attributes:
16+
label: Expected Behavior *
17+
description: A clear and concise description of what you expected to happen.
18+
placeholder: Tell us what you expected!
19+
validations:
20+
required: true
21+
- type: textarea
22+
id: observed
23+
attributes:
24+
label: Observed Behavior *
25+
description: A clear and concise description of what happened instead.
26+
placeholder: Tell us what you observed!
27+
validations:
28+
required: true
29+
- type: textarea
30+
id: steps
31+
attributes:
32+
label: Steps to Reproduce
33+
description: Steps to reproduce the behavior.
34+
placeholder: Tell us how to reproduce the issue!
35+
validations:
36+
required: false
37+
- type: textarea
38+
id: context
39+
attributes:
40+
label: Context Information
41+
description: Add any other context about the problem here.
42+
validations:
43+
required: false
44+
- type: textarea
45+
id: logs
46+
attributes:
47+
label: Relevant log output
48+
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
49+
render: shell
50+
validations:
51+
required: false
52+
- type: textarea
53+
id: screenshots
54+
attributes:
55+
label: Screenshots
56+
description: If applicable, add screenshots or other information to help explain your problem.
57+
validations:
58+
required: false
59+
- type: markdown
60+
attributes:
61+
value: |
62+
<sup>_* These fields are mandatory, without filling them it is not possible to create the issue._</sup>

‎connector-ui/.github/ISSUE_TEMPLATE/config.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: true

‎connector-ui/.github/ISSUE_TEMPLATE/documentation.md

+30
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Documentation Update Request
3+
about: Create a report to help us improve our documentation
4+
title: ""
5+
labels: "task/documentation"
6+
assignees: ""
7+
---
8+
9+
# Documentation Update Request
10+
11+
## Description
12+
<!-- Provide a brief overview of the documentation update request. What section or topic needs to be updated? -->
13+
14+
## Current Documentation
15+
<!--- Insert a link to the current documentation related to the topic. -->
16+
17+
## Proposed Changes
18+
<!-- Describe the changes that need to be made. Be as specific as possible. -->
19+
20+
## Justification
21+
<!-- Explain why these changes are necessary. Is there new information, outdated content, or improvements needed for clarity? -->
22+
23+
## Additional Context
24+
<!-- Include any additional context, screenshots, examples, or references that might help in understanding the update request. -->
25+
26+
## Deadline
27+
<!-- Set a deadline for completing the documentation update, if applicable. -->
28+
29+
## Notes
30+
<!-- Any additional notes or instructions for the team regarding this documentation update request. -->

‎connector-ui/.github/ISSUE_TEMPLATE/epic_template.md

+46
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
name: Epic
3+
about: Help us with new ideas
4+
title: ""
5+
labels: "kind/epic"
6+
assignees: ""
7+
---
8+
9+
# Epic
10+
11+
## Description
12+
<!-- Brief summary of what this Epic is, whether it's a larger project, goal, or user story. Describe the job to be done, which persona this Epic is mainly for, or if more multiple, break it down by user and job story. -->
13+
14+
### Requirements
15+
<!-- Which requirements do you have to be fulfilled? -->
16+
<!-- Which security-related requirements must be satisfied? -->
17+
18+
## Work Breakdown
19+
<!-- If you already know what needs to be done, plase add a tasklist. -->
20+
21+
```[tasklist]
22+
### Stories
23+
- [ ] Create Stories which can be converted into issues
24+
```
25+
26+
### Security Constraints
27+
<!-- Which constraints can be checked that must be covered by the work breakdown? -->
28+
- [ ] Final solution design has been challenged for security related topics
29+
30+
## Initiative / goal
31+
<!-- Describe how this Epic impacts an initiative the business is working on. -->
32+
33+
### Hypothesis
34+
<!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->
35+
36+
## Acceptance criteria and must have scope
37+
<!-- Define what is a must-have for launch and in-scope (e.g. security-related tasks like successful pen-tests). Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->
38+
39+
## Stakeholders
40+
<!-- Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project. -->
41+
42+
## Timeline
43+
<!-- What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date. -->
44+
45+
## Need for refinement
46+
<!-- Which questions are open? From whom do you need more input to fully specify the epic? -->

‎connector-ui/.github/ISSUE_TEMPLATE/feature_request.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: Feature Request
3+
about: Help us with new features
4+
title: ""
5+
labels: "kind/enhancement"
6+
assignees: ""
7+
---
8+
9+
# Feature Request
10+
11+
## Description
12+
<!-- A clear and concise description of what the customer wants to happen. Example below. -->
13+
- As a USER who PRECONDITIONS, I want to DO_THING, so I can ACCOMPLISH_GOAL.
14+
15+
## Which Areas Would Be Affected?
16+
<!-- e.g., DPF, CI, build, transfer, etc. -->
17+
18+
## Why Is the Feature Desired?
19+
<!-- Are there any requirements? -->
20+
21+
## How does this tie into our current product?
22+
<!-- Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new markets and innovative ideas? -->
23+
24+
## Stakeholders
25+
<!-- Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature? -->
26+
27+
## Solution Proposal and Work Breakdown
28+
<!-- If you already know what needs to be done, please add a tasklist. -->
29+
30+
```[tasklist]
31+
- [ ] Fix the GitHub Projects Labels, Sprint and other Metadata
32+
- [ ] Refine a Solution Proposal / Work Breakdown
33+
- [ ] (For Tech Team): Include acceptance criteria for the sub-tasks of the work breakdown
34+
- [ ] Add security related tasks and checks
35+
- [ ] Final solution design has been challenged for security related topics
36+
```

‎connector-ui/.github/ISSUE_TEMPLATE/process.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Refine Process Request
3+
about: Existing processes must be adapted or new ones created
4+
title: ""
5+
labels: ["task/refine-process","task/documentation"]
6+
assignees: ""
7+
---
8+
9+
# Process Refinement Request
10+
11+
## Description
12+
<!-- Provide a brief description of the process that needs refinement and the reason behind it. -->
13+
14+
## Current State
15+
<!-- Describe the current state of the process, including any pain points or inefficiencies. -->
16+
17+
## Proposed Changes
18+
<!-- Outline the changes that need to be made to improve the process. Be as specific as possible. -->
19+
20+
## Related Issues or PRs
21+
<!-- If there are any related issues or pull requests, mention them here. -->
22+
23+
## Additional Information
24+
<!-- Any additional information or context that may be helpful for understanding the issue. -->

‎connector-ui/.github/ISSUE_TEMPLATE/release.md

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: Release
3+
about: Create an issue to track a release process.
4+
title: "Release x.y.z"
5+
labels: ["task/release", "scope/ce"]
6+
assignees: ""
7+
---
8+
9+
# Release
10+
11+
## Work Breakdown
12+
13+
Feel free to edit this release checklist in-progress depending on what tasks need to be done:
14+
- [ ] Decide a release version depending on major/minor/patch changes in the CHANGELOG.md.
15+
- [ ] Update this issue's title to the new version
16+
- [ ] `release-prep` PR:
17+
- [ ] Update the CHANGELOG.md.
18+
- [ ] Check that all the entries have a link to an issue or a pull request.
19+
- [ ] Add a clean `Unreleased` version.
20+
- [ ] Add the version to the old section.
21+
- [ ] Add the current date to the old version.
22+
- [ ] Reorder, reword or combine changelog entries from a product perspective for consistency.
23+
- [ ] Check the [Dependabot Alerts](https://github.com/sovity/edc-ui/security/dependabot) for anything fixable pre-release.
24+
- [ ] Write or review a `Deployment Migration Notes` section.
25+
- [ ] Write or review a release summary.
26+
- [ ] Remove empty sections from the patch notes.
27+
- [ ] Review the Screenshots in the Readme and update them if necessary.
28+
- [ ] Merge the `release-prep` PR.
29+
- [ ] Wait for the main branch to be green.
30+
- [ ] Create a release and re-use the changelog section as release description, and the version as title.
31+
- [ ] Check if the pipeline built the release versions in the Actions-Section (or you won't see it).
32+
- [ ] Revisit the changed list of tasks and compare it with [.github/ISSUE_TEMPLATE/release.md](https://github.com/sovity/edc-ui/blob/main/.github/ISSUE_TEMPLATE/release.md). Propose changes where it
33+
makes sense.
34+
- [ ] Close this issue.

‎connector-ui/.github/PULL_REQUEST_TEMPLATE.md

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
_What issues does this PR close?_
2+
3+
4+
```[tasklist]
5+
### Checklist
6+
- [ ] The PR title is short and expressive.
7+
- [ ] I have updated the CHANGELOG.md and linked the changes to their issues. See [changelog_update.md](https://github.com/sovity/authority-portal/blob/main/docs/dev/changelog_updates.md) for more information.
8+
- [ ] I have updated the Deployment Migration Notes Section in the CHANGELOG.md for any configuration / external API changes.
9+
- [ ] I have performed a **self-review**
10+
```

‎connector-ui/.github/workflows/add_issue_to_project.yml

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
name: Add issue to project action
2+
3+
on:
4+
issues:
5+
types:
6+
- opened
7+
8+
jobs:
9+
add_issue_to_project:
10+
if: "!(startsWith(github.event.issue.title, '[Zammad Ticket') && github.event.issue.user.login == 'sovitybot')"
11+
name: add_issue_to_project
12+
runs-on: ubuntu-latest
13+
steps:
14+
- uses: actions/add-to-project@v1.0.2
15+
with:
16+
project-url: https://github.com/orgs/sovity/projects/9
17+
github-token: ${{ secrets.ADD_ISSUE_TO_PROJECT_PAT }}

‎connector-ui/.github/workflows/automerge.yml

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
name: auto-merge
2+
3+
on:
4+
pull_request:
5+
6+
jobs:
7+
automerge:
8+
runs-on: ubuntu-latest
9+
continue-on-error: true
10+
permissions:
11+
pull-requests: write
12+
contents: write
13+
steps:
14+
- uses: fastify/github-action-merge-dependabot@v3
15+
continue-on-error: true
16+
with:
17+
target: patch
18+

0 commit comments

Comments
 (0)