Matthias Mair
Matthias Mair
There is immense complexity in generalising this for all possible use cases due to InvenTree's flexibility in BOMs. You can have variants, multiple suppliers and manufacturers for each part, stacked...
Supporting generic model relations would be nice, that way plugins could use reports easily.
@SchrodingersGat this needs to be called out as breaking for plugins that call complete_order in the release notes as the effect changes
Related https://github.com/inventree/InvenTree/issues/5884 https://github.com/inventree/InvenTree/issues/2777
Maybe this could be structured as a generic similar to states - consistent code docstrings, fully covered with tests within the module. I would also remove the backend distinction between...
Could also be part of https://github.com/inventree/InvenTree/issues/6417
@SchrodingersGat I added the issues/PR that currently cover the tasks
@SchrodingersGat do you think this should also apply to the code/database level? We have a lot of duplication in this area currently. Nearly half of our Python code-duplication is between...
@SchrodingersGat what is your general position on keeping a dedicated CHANGELOG file? Should this target 0.16.0?
I think everything that is breaking and any major new feature (everything we would put into the release notes/blog) should be included