Allow stock transfer to merge into existing stock (optional) #6951

[neilbeukes]

As requested in #6951, I am providing an option when transferring stock between locations, to optionally merge into the first available stock of the same type (of part).

New parts added.

• Option on transfer modal to enable merge after transfer
• Global settings line to set the default state of the option on the modal
• Tracking entries to signal transfer of stock
• Tests for new transfer-merge logic.

This is will change existing behavior as follows.

If merge is toggled

• Look for first matching stock item in destination location.
  • If matching stock found, perform a standard merge between transferred stock and existing matched stock.
  • if no matching stock found then follow existing transfer logic.
• History of destination stock remains the same, and get another tracking event signalling stock transferred and from where.

If merged is not toggled

• Existing behaviour stays intact i.e transferred stock will become its "own" stock in the destination location.

Some images:

Global settings

Modal with merge enabled on transfer

Middle event is an example of a merged transfer

[netlify]

✅ Deploy Preview for inventree-web-pui-preview ready!

Name	Link
🔨 Latest commit	2a3b95f
🔍 Latest deploy log	https://app.netlify.com/projects/inventree-web-pui-preview/deploys/6a1df28cd47cf00008b132a1
😎 Deploy Preview	https://deploy-preview-12022--inventree-web-pui-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 92 (🟢 up 1 from production) Accessibility: 82 (no change from production) Best Practices: 100 (no change from production) SEO: 78 (no change from production) PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[neilbeukes]

Oh I see some builds failing, ill take a look at those. I'm assuming I need to also update docs with added functionality.

[codecov]

Codecov Report

❌ Patch coverage is 91.46341% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.43%. Comparing base (d2bec03) to head (19db981).

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #12022   +/-   ##
=======================================
  Coverage   91.42%   91.43%           
=======================================
  Files         974      974           
  Lines       51915    51995   +80     
=======================================
+ Hits        47465    47541   +76     
- Misses       4450     4454    +4     

Flag	Coverage Δ
backend	90.44% <91.46%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Backend Apps	91.75% <91.46%> (-0.01%)	⬇️
Backend General	93.36% <ø> (ø)
Frontend	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[matmair]

1. you need to bump the version in api_version.py and add a entry in the docstring below
2. you need to add a doc section for STOCK_MERGE_ON_TRANSFER - see global.md

[matmair]

This feels like it will be very hard to trace back and also like a data loss

[SchrodingersGat]

Any newlines are stripped out from char fields too

[neilbeukes]

You guys are right, thanks for pointing it out. Stripping the existing tracking event and replacing it with a lesser detailed event makes no sense. Im mostly reusing the existing event now.

[SchrodingersGat]

@neilbeukes looking good! Only issue is that the code is not meeting style guidelines:

If you run pre-commit install in your local repo, it will automatically format the code for you on each git commit.