Stylizing Debug Info for barcode/po-recieve/ API

[Idea-Junkie]

Hello all,

I am working on API Debug for one of the barcode scans and wanted everyone's thoughts on this style of comments below, I will obviously be adding more as this is just a general idea,

API addition

The added error log as seen below will introduce "Plugin Debug Info" for suppliers if the suppliers plugin fails to find a matching item

"DigiKeyBarcodePlugin" will be replaced by whatever the name of the plugin was tested on the suppliers barcode scanned with the " Debug" Appended at the end

Possible Issues

With this being said I realize if they have many different plugins that do not work it could get filled up very fast, I will be thinking more on if I need to find a better and shorter way of doing this for the API response and should leave those to the debug logs.

Any feedback would be appreciated as well!

[matmair]

So there will be one log per plugin? We alone ship 4 with core, this does not scale

[Idea-Junkie]

Yes, that is what I have currently since I was messing with only one plugin but wanted it to scale; however, I did understand that it could cause issues, and already had a idea for that solution, which is if the PO with its associated supplier is found in the barcode, then the Debug log pops up for that plugin.

As well as an error for if it searches all plugins and doesnt find a matching PO then it produces a "Purchase Order not found" as the pop up error or something similar. Does that sound more scalable?

Thanks for taking a look at this as well!

[Idea-Junkie]

Update

I have updated it to include only the info for the plugin that finds a PO or a Supplier part in the barcode of that plugin. I have all the built in barcode plugins active as well to test that. It seems to be working quite well.

InvenTree-Version: 1.3.0 dev
Django Version: 5.2.11
Database: django.db.backends.postgresql
Debug-Mode: True
Deployed using Docker: False
Platform: Linux-5.15.153.1-microsoft-standard-WSL2-x86_64-with-glibc2.36
Installer: DEV
Active plugins: [{"name":"InvenTreeBarcode","slug":"inventreebarcode","version":"2.2.0"},{"name":"BOM Exporter","slug":"bom-exporter","version":"1.1.0"},{"name":"InvenTree Exporter","slug":"inventree-exporter","version":"1.0.0"},{"name":"Parameter Exporter","slug":"parameter-exporter","version":"2.0.0"},{"name":"InvenTreeEmailNotifications","slug":"inventree-email-notification","version":"1.0.0"},{"name":"InvenTreeUINotifications","slug":"inventree-ui-notification","version":"1.0.0"},{"name":"InvenTreeCurrencyExchange","slug":"inventreecurrencyexchange","version":"1.0.0"},{"name":"InvenTreeMachines","slug":"inventree-machines","version":"1.0.0"},{"name":"InvenTreeLabel","slug":"inventreelabel","version":"1.1.0"},{"name":"InvenTreeLabelMachine","slug":"inventreelabelmachine","version":"1.0.0"},{"name":"DigiKeyBarcodePlugin","slug":"digikeyplugin","version":"1.0.1"},{"name":"LCSCBarcodePlugin","slug":"lcscplugin","version":"1.0.1"},{"name":"MouserBarcodePlugin","slug":"mouserplugin","version":"1.0.1"},{"name":"TMEBarcodePlugin","slug":"tmeplugin","version":"1.0.1"}]

This fixes the issue brought up in the original post as well

Mobile Error Pop-Up

The original line was too long but with a carriage return added to it, it is readable on the app as well

New Errors Included

Purchase order Found, No supplier Part Match

This pops up if a Supplier is found with the PO attached, but a supplier part is not included in any line items on the PO

Supplier Part Found, No Purchase Order Match

This pops up if a Supplier is found with the associated supplier part, but the PO was not found

Notes

With this now in a working condition, I will be making some small tweaks to make the code follow the peps python guideline as well as include debug logs for the server, and then will submit a PR request.

Also Question, can I Include documentation updates on the same PR request as well? or is that handled separately?

As well as any feedback is appreciated!

[matmair]

Without a PR it is hard to make any in depth comments but sounds like a reasonable ux improvement.

Regarding pep style: we use ruff for opinionated formatting and that can be set up to be automatic, see our contribution guide https://docs.inventree.org/en/stable/develop/contributing/

Regarding docs: updating the documentation in the same PR is encouraged