[PUI/Feature] Integrate Part "Default Location" into UX

[LavissaWoW]

Closes #5928
Closes #5938

• Add Default Parts filter to API
• [PUI] Add Default Parts panel to Stock Location View
• Add "Transfer to default location" functionality [PUI] [CUI?]
• Add Default location checkbox when splitting stock items
• Propagate default location from parent category tree to parts

[netlify]

✅ Deploy Preview for inventree-web-pui-preview canceled.

Name	Link
🔨 Latest commit	9ef7454
🔍 Latest deploy log	https://app.netlify.com/sites/inventree-web-pui-preview/deploys/65f3823e6741ce000821f30e

[LavissaWoW]

@SchrodingersGat @matmair @wolflu05
Anyone currently implementing the following in PUI?
Stock Item Detail Panel
Stock Item Transfer Modal
Part Category Detail/List
Part Category Creation and Edit Modal

To do all the work I'm planning here, I'll have to add some elements to Stock Items, Part Categories, and additionally Purchase Orders. I don't want to overlap work others are doing :)
If these are TBD atm, I'll take a stab at implementing them, else I'll add the functionality to those when they are merged in.

[SchrodingersGat]

@LavissaWoW I do not have any active progress on any of the items you list. We have not implemented any "detail" pages yet - I would be keen to see if we can develop a standard component or set of components for rendering a "detail" view - primarily for UI consistency.

If you want to tackle a detail page in the new UI that's great 👍

[github-actions]

This PR seems stale. Please react to show this is still important.

[SchrodingersGat]

@LavissaWoW not stale, right?

[LavissaWoW]

Not stale indeed. Need to sort out priorities here though. I got some backend shenanigans planned, and several frontend changes.
Depending on the frontend change, prio would be on PUI.

[LavissaWoW]

@SchrodingersGat I'm inclined to ignore CUI with this.
I'd rather not spend a lot of time digging into vanilla JS that we're phasing out soon.
I.e. #5938 would be more easily implemented in PUI rather than CUI. (Update location field when changing category)
This sentiment does however mean that this PR will rely on some PUI work.

[LavissaWoW]

@wolflu05 @SchrodingersGat
I've implemented a form field type for rendering array-based values as tables.
Relevant changes are in
TableField.tsx
StockForms.tsx:stockTransferFields
StockForms.tsx:StockOperationsRow
ApiFormField.tsx (case: 'table')

The use for this is forms where we pass arrays of objects ot the API. For this PR, I'll use it for Stock operations.
Let me know what you think.

[wolflu05]

Nice idea to implement this as a field type. After reading array field, I first was thinking something different, but after reading the implementation the name table makes sense. I'm only concerned about that this is actually not a real form, you're just using it to display a modal? But I'm fine with it.

[LavissaWoW]

It is a proper form for the /stock/transfer POST endpoint.
Looks like this with only 1 item in the table :)

[SchrodingersGat]

@LavissaWoW the table form UI looks really good :)

[LavissaWoW]

I should probably handle the category defaults for CUI too. Feel free to review, though. I'll add one last commit asap

[LavissaWoW]

@SchrodingersGat All good, this is ready now

[SchrodingersGat]

@LavissaWoW this is great, such a lot of work here :)

Review below, there's a few points and suggestions but nothing major!

Stock Table Actions

When no items are selected, either:

a) Disable the "actions" column, or
b) Select all stock items in the table by default

Otherwise, you get this "no entries available" message

In fact, this goes for other table forms too. If there are no available lines when opening the form, we need a "default selection" here.

Receive Line Items

Really good! Perhaps the modal should be wider by default?

Receive Line Items - Default Location

Looks like the "default location" does not propagate here?

This part does have a "default location" set:

Although it should also work if there is a "default category location"

Category Detail Page

Should display the "default location" for the category (or upstream parent category as required). Currently not displayed:

[LavissaWoW]

@SchrodingersGat Aside from the propagating default to PO line, and the category detail panel, (I'll fix those) I looked at most of this myself.

The APIForm modals have a default width defined deeply nested within the framework we've created to display them. I wanted the PO Receive to be wider, and the lack of width is why I hid the Status field within a toggleable extra row. I can look into if it's possible to add some props to allow for oversizing the modals?

Table actions I concluded it's not possible to get all records from a given table as things are now.
Out custom useTable hook holds data for any given table, but it doesn't hold "all records" afaik. Records are fetched in the InvenTreeTable component, so the modals can't access the raw records from StockItemTable/POLineTable/etc.
Solution: Either see if an allRecords/pageRecords can be added to useTable, or disable actions when selectedRecords is empty? This includes PO receive too.

[SchrodingersGat]

or disable actions when selectedRecords is empty? This includes PO receive too.

This is probably the best approach for now, until (if) we can work out a different approach. At least visually the user should be aware that they have no records selected and thus cannot perform actions

[LavissaWoW]

@SchrodingersGat I was initially struggling to reproduce the PO line location, but it turns out I made a couple of mistakes, and it was even more broken than you experienced. The PO lines have a destination and a destination_detail. The latter can be set without the former being set. If the latter is set, and the former not, one of the following is true:

1. The part has a default location
2. Some stock has already been received for this line

My logic was off in my assumptions here, and I found myself with test data where previously received stock had been placed at the default location. So some of my logic indicated default, while it was actually previously received that triggered it. Additionally, the queryset annotation I added to StockItem ofc. didn't magically carry over to POLineItems, so category_default_location never even existed on line.part_detail

Fix incoming shortly

[SchrodingersGat]

@LavissaWoW I realize that part of the issue was that I was viewing the netlify preview - which talks to the demo server, which in turn does not have the latest API. So, this will explain the discrepencies.

[SchrodingersGat]

@LavissaWoW thanks again for the great work here!