Extract Layout: Code restructure for readability and using actual containers as detected by integration

[BigRoy]

Changelog Description

Extract Layout: Code restructure for readability and using actual containers as detected by integration

Additional review information

Still draft

Fix #121

Testing notes:

1. Extract Layout should work
2. The content should be loaded correctly.

[BigRoy]

@antirotor @moonyuet can you let me know what you think of these code changes to clean this up? This also fixes #121 (although purely that fix would've been smaller) but a lot of the code was quite unclear what it tried to do.

This PR does remove the usage of the groupLoadedAssets toggle since I couldn't really figure out what it did. It felt like it was solely used to detect containers in a group? But was that because there were the default parent asset groups above them from loading AYON references? Or was there a particular use case there @moonyuet ?

[moonyuet]

@antirotor @moonyuet can you let me know what you think of these code changes to clean this up? This also fixes #121 (although purely that fix would've been smaller) but a lot of the code was quite unclear what it tried to do.

This PR does remove the usage of the groupLoadedAssets toggle since I couldn't really figure out what it did. It felt like it was solely used to detect containers in a group? But was that because there were the default parent asset groups above them from loading AYON references? Or was there a particular use case there @moonyuet ?

@antirotor would know a bit more about the use case. I usually turn this off and publish.

[moonyuet]

I tested with publishing layout with this PR, it is successful but.
https://github.com/user-attachments/assets/703cdaaa-e64a-4e02-ad59-b4050e92d791

It might be helpful if you can take a look at the data below
the v006 layout is published from layout extractor in the develop branch
il_lib_layoutWorkfileArt_v006.json

the latest version is published from layout extractor in this branch
il_lib_layoutWorkfileArt_v008.json

[BigRoy]

Thanks @moonyuet - I fixed the matrix basis being integers, now they are floats again. I didn't care much about the empty object_transform key existing even if empty. Seems like a good thing if the data structure would remain a bit consistent in that area. Would you like me to pup the key if it is empty instead?

Also, I'm quite surprised it actually worked and this is the only difference in the data 🤯

[antirotor]

with the groupLoadedAsset - it is also set in Create Multishot Layout but used only here. I am ok to remove it and observe. In case it will be missed by someone, lets clearly define what it should do, implement and document it again.

[antirotor]

I'd say we don't need that anymore. We can use pure dataclasses, no? I think the idea was to eventually get rid of this dependency.

[BigRoy]

I'd say we don't need that anymore. We can use pure dataclasses, no? I think the idea was to eventually get rid of this dependency.

Unfortunately - I think we'd then face that pyblish mixed with dataclasses and from __future__ import annotations issue, right? That's why I went for attr here.

[antirotor]

This was fixed already in pyblish-base - pyblish/pyblish-base#403

[antirotor]

.... ah but not released! 😱

[BigRoy]

Merging this as is @antirotor - I think we can improve later if need be.

[LiborBatek]

Works for me...both .ma and .json been working without any glitches.

LGTM