Open jmwright opened 5 years ago
@m30-jrs Starting to look at this and what I think I'm seeing is that our current example BoM yaml files are not in sync with the design criteria laid out in the DoF and Sliderule repos. For instance, the current files will end up with naming collisions when amalgamated, requiring namespaces because the IDs are not in place yet. Do you have the documentation for the BoM model revamped yet?
Thanks for the heads up, i have been working on the modeling of activities so we can test out assembly instructions instead of BoM data format (the instructions work is informing the data model).
Let me wrap up the example I am working on and then I will update data structures related to components including BoM data.
Once #6 is implemented properly, a function needs to be added that will crawl the entire project structure and amalgamate the BoMs from all the sub-components. It's assumed that the amalgamated model will be stored in the
dist
directory. The BoMs need to be amalgamated in an order that makes sense, which is at the heart of #6A potential nomenclature for this might be "build". This specific function would be
build_bom
.