Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

attempt 1 at childPaths rework #19

Closed
wants to merge 2 commits into from
Closed

attempt 1 at childPaths rework #19

wants to merge 2 commits into from

Conversation

adamjanicki2
Copy link
Contributor

Will close #18 as well as #17 in the process

Copy link

netlify bot commented Mar 11, 2024

Deploy Preview for treecle ready!

Name Link
🔨 Latest commit 676928d
🔍 Latest deploy log https://app.netlify.com/sites/treecle/deploys/65ef991c3ffe320008b8ebe9
😎 Deploy Preview https://deploy-preview-19--treecle.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

else {
return Object.values(node).flat();
}
return childPaths.call(this, node).map(({node}) => node);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is technically less efficient by a factor of 2, however since the amount of child is roughly constant I think it's well worth the tradeoff since we don't want this getting out of sync with childPaths

@adamjanicki2 adamjanicki2 removed the request for review from LeaVerou April 1, 2024 17:32
@adamjanicki2 adamjanicki2 deleted the childpaths branch April 1, 2024 17:33
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.

Supporting different schemas around getting child nodes
1 participant