-
-
Notifications
You must be signed in to change notification settings - Fork 325
Creating v4-dev branch #417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v4-dev
Are you sure you want to change the base?
Conversation
assessment: activity.assessment.toString() || '', | ||
level: activity.level || 0, | ||
teamImplementation: activity.implementation || {}, | ||
// teamsEvidence: activity.teamsEvidence || {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, this is part of the mapping.componentn.ts
and we do not show any team progress or evidence on that page. That is why it was not included here.
Improved dependency graph
@vbakke I am not sure about "author" as an attribute due to data protection laws. |
At some point we might include a version in the data repository to the yaml. That is not so easy, because the activities.yaml/generated.yaml is not prepared for extra field (used to be in meta.yaml, which is moved to this repo) |
The author is public in github anyway. But then again, it is not any need for that in my opinion, so that is fine to leave out author. Just to verify: Is is regarding displaying version number and realse date of the DSOMM app, lets say on an About page, @wurstbrot ?
|
EDIT: Moved my comment to a line in |
@@ -0,0 +1,8911 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Versioning of DSOMM-data's activity-list
At some point we might include a version in the data repository to the yaml. That is not so easy, because the activities.yaml/generated.yaml is not prepared for extra field (used to be in meta.yaml, which is moved to this repo)
Yes, I know. I've tried to find a way, but I think I ended up with two suggestions, @wurstbrot.
A) treat meta
in genetared.yaml/activities.yaml differently and extract this in the new LoaderService. (Small chance we will ever get a dimension called meta)
meta:
version: x.x.x.
released: 2025-09-28
Build and Deployment:
Build:
Building and testing of artifacts in virtual environments:
etc
B) use yaml's "multiple documents" feature. Something like:
---
meta:
version: x.x.x.
released: 2025-09-28
...
---
Build and Deployment:
Build:
Building and testing of artifacts in virtual environments:
etc
...
Both alternatives need an adjustment of in the LoaderService. But not a big change in the Angualr application
Dark mode added, @wurstbrot, @0x41head. And nodes ae now clickable, so that one can navigate between depending nodes. 🙂 |
Let's try again. This time, creating a pull request (/merge request) into
v4-dev
. I decided to call this branchv4-dev
so that we can reservev4
to when we are ready to release.