Closed maxhbr closed 4 months ago
I agree tools should support the inverse direction for relationships in the parsing tools.
There are scenarios where the inverse relationship is created since the relationship is not known when the first component is created making it more convenient to add the reverse relationship to the second component rather than amending the first.
In the case of no inverse relationships - I personally think it would be OK if the tool just output a relationship type that isn't in the spec, but makes sense - e.g. BUILD_DEPENDS_ON
for BUILD_DEPENDENCY_OF
.
Another reason to support reverse relationships is preparing for the future: SPDXv3 removes the "dual" relationships.
There is still a DEPENDS_ON
but no more DEPENDENCY_OF
, for example.
Having both would unnecessarily complicate things, as there are (till now) 64 relationship types and we don't want to have 64 reverse ones.
ping @puerco , can you please chime in here and clarify your opinion on the ticket?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Hey, I think this is still valid. Can someone please have a look?
@maxhbr yep seems valid, are you willing to open a pr to get this fixed?
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
There are some Relationships like
TEST_DEPENDENCY_OF
are pointing from the test dependency. These relationships are not represented and visualized correctly. Especially, if some SPDX document prefersDEPENDENCY_OF
overDEPENDS_ON
, it might be listed as having no relationships.What happened:
As discussed in https://github.com/npm/cli/issues/6867#issuecomment-1751871862 the following two sections from SPDX documents are equivalent but yield different representations in this tool.
Variant 1
visualized as
Variant 2
visualized as
What you expected to happen:
As they are describing the equivalent graph I would expect both to have similar representations in the tool. But the tool fails to identify that the second one has relationships at all.
There are some which could just be "normalized" on parsing, e.g. a
DEPENDENCY_OF
relationship could be converted to itsDEPENDS_ON
representation.Some other types have no inverse, like
BUILD_DEPENDENCY_OF
,DEV_DEPENDENCY_OF
,OPTIONAL_DEPENDENCY_OF
,PROVIDED_DEPENDENCY_OF
andTEST_DEPENDENCY_OF
. For those there should be a way to show arrows which are pointing from the "smaller" to the "bigger". Maybe by introducing names for the inverse or with some ASCII art.