fix: correctly calculate the initial status of uploaded file #580
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: When uploading a new file, the status was incorrectly showing as "Archived" instead of "Processing" or "Publishing".
Root Cause: In the objectStatus function, the check for "Archived"
(archivedNodes === totalNodes)came before the check for "Processing". When a file is first uploaded:archivedNodesandtotalNodescan benullor0null === nulland0 === 0both evaluate to true in JavaScriptFix: Reordered the conditions to check for the "Processing" state first. Now the logic is:
totalNodesoruploadedNodesisnullor0→ ProcessingarchivedNodes === totalNodes(and both are valid positive numbers) → ArchiveduploadedNodes === totalNodes(all published but not all archived) → ArchivingThis matches the documented file lifecycle in file-lifecycle.md:
Fixes #383