Skip to content
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

Flat merging can result in duplicate BOM refs #82

Open
coderpatros opened this issue Jul 20, 2021 · 1 comment · May be fixed by #245
Open

Flat merging can result in duplicate BOM refs #82

coderpatros opened this issue Jul 20, 2021 · 1 comment · May be fixed by #245

Comments

@coderpatros
Copy link
Member

Not sure how to handle this. For hierarchical merging the top level component information can be used to "namespace" BOM refs.

Maybe requires supporting passing in namespace values for each BOM or optionally generating a random namespace.

I personally don't like the latter as it will drastically change BOM refs between runs. But maybe that's not really an issue given they are just used to identify elements within a single instance of a BOM.

@fnxpt
Copy link

fnxpt commented Feb 16, 2023

This should be fixed with #199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants