Skip to content

Fix yds load for nested object when current working directory is an object and element path is empty - #39

Merged
j-simmons-phd merged 5 commits into
mainfrom
fix-yds-load-for-nested-object-when-current-working-directory-is-an-object-and-element-path-is-empty
Aug 4, 2026
Merged

Fix yds load for nested object when current working directory is an object and element path is empty#39
j-simmons-phd merged 5 commits into
mainfrom
fix-yds-load-for-nested-object-when-current-working-directory-is-an-object-and-element-path-is-empty

Conversation

@capsulecorplab

Copy link
Copy Markdown
Collaborator

resolves #37

@capsulecorplab capsulecorplab added the bug-fix Fixes a bug label Aug 1, 2026
@j-simmons-phd
j-simmons-phd merged commit 80bcf1e into main Aug 4, 2026
2 checks passed
@j-simmons-phd
j-simmons-phd deleted the fix-yds-load-for-nested-object-when-current-working-directory-is-an-object-and-element-path-is-empty branch August 4, 2026 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug-fix Fixes a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

yds-load not loading nested objects for depth higher than 0 when current working directory is an object and element path is empty

2 participants