-
-
Notifications
You must be signed in to change notification settings - Fork 211
fix: postProcess dependencies to correct root deps #2199
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: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Unsure if this is better suited as a post bom step.... Or, if it would be better to add a placeholder component and then update the dependsOn refs |
@setchy, looks a bit different indeed. Usually with vibe-coding, get the AI to generate valid test cases by feeding some examples. Then iterate to solve the test cases gradually increasing the complexity. |
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Signed-off-by: Adam Setch <adam.setch@outlook.com>
projectName
and projectVersion
specifiedSigned-off-by: Adam Setch <adam.setch@outlook.com>
Signed-off-by: Adam Setch <adam.setch@outlook.com>
@prabhu - with a fresh set of eyes I've reworked the enhancement. Moved it to be a postProcess step that parses and corrects any parent dependencies to ensure a connected graph |
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Signed-off-by: Adam Setch <adam.setch@outlook.com>
Any ideas why the tests are failing? |
I dont actually 🤷♂️ |
Add a new postProcess step which will parse all dependencies and
dependsOn
)ref
/bom-ref
Should help with #489 in constructing a connected dependency graph