Replies: 1 comment 4 replies
-
Do you have a small example to check this? outputs:
- name: 'bom_internal'
comment: "Bill of Materials in CSV format"
type: bom
dir: BoM
options:
fit_field: BOM I see:
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The documentation says:
If I define a
bom
output with thefit_field
defined, the resulting BOM does not ignore DNF components (even thoughignore_dnf: true
is set):However, if I add
dnf_filter: _kibom_dnf_BOM
, then DNF components are correctly ignored in the resulting BOM:I would assume that by defining
fit_field: BOM
, the internal_kibom_dnf
filter should effectively function the same as a filter named_kibom_dnf_BOM
, sodnf_filter: _kibom_dnf_BOM
should be unnecessary.Furthermore, if I define a
kibom
output withfit_field: BOM
, the DNF components are correctly ignored in the resulting BOM:It seems like there is a difference between the behavior of
bom
vs.kibom
outputs, i.e.bom
seems to require an explicitdnf_filter: _kibom_dnf_BOM
whereaskibom
seems to implicitly create this filter based on thefit_field: BOM
option.Is this intentional? If not, could the
bom
output be fixed so that whenfit_field: BOM
is specified, the internal_kibom_dnf
filter behaves like_kibom_dnf_BOM
(i.e.dnf_filter: _kibom_dnf_BOM
doesn't need to be specified also)?Beta Was this translation helpful? Give feedback.
All reactions