Skip to content

Improve Handling of Parent-Child Relationships#457

Open
Hoikas wants to merge 4 commits into
H-uru:masterfrom
Hoikas:parent_object_sanity
Open

Improve Handling of Parent-Child Relationships#457
Hoikas wants to merge 4 commits into
H-uru:masterfrom
Hoikas:parent_object_sanity

Conversation

@Hoikas

@Hoikas Hoikas commented Jul 6, 2026

Copy link
Copy Markdown
Member

This PR improves the parent/child object process by showing a noisy warning at the end of the export if an object is parented to an object in another page. Also, for safety, if a parent object is disabled either explicitly or by being in a disabled page, that child object is implicitly disabled, and a warning is printed to the log.

These mitigations should fix #453.

Hoikas added 4 commits July 6, 2026 17:16
The code was treating the nonfatal error raised at the end of the export
process like any other exception and printing an aborted/failure
indicated message, along with the errors. In reality, these are already
printed out, so don't do anything special with these.
If the parent object is disabled or the page the parent object is in is
disabled, then we should probably not export that child object at all.
We have reports of child objects not being in the same page as parent
objects causing issues, so we'll also surface that as a more concerning
non-fatal error that actually pops up at the end of the export process.
This really only detects the case of the parent object being explicitly
turned off. That's the big one, to be honest.
Sometimes, we really want to know "is this object going to be
exported?". The Plasma Object "enabled" really just means "the user
wants this to export", and the "is_tree_enabled" means "it looks like
this object can export".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cross Page PRP Referenes cause Sorting Order Issues.

1 participant