Eagerly processing tree artifacts in manifest.read_entries_from
?
#933
rbeasley-avgo
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
While working on PR #928 in service of #927, I discovered #932. Consequently I'm closing PR #928 in favor of providing a more comprehensive fix. That's what this discussion will be about.
So, what if we moved the handling of tree artifacts from each builder's
add_tree
method tomanifest.read_entries_from
? Here's the gist:read_entries_from
encounters a tree artifact, it will walk the tree artifact and synthesize manifest entries.add_tree
methods.Here's a hacky sketch:
What do folks think?
Beta Was this translation helpful? Give feedback.
All reactions