Skip to content

Conversation

justinsb
Copy link
Contributor

@justinsb justinsb commented May 6, 2022

A slightly awkward implementation, but this allows for direct creation of packages without a base.

A slightly awkward implementation, but this allows for direction
creation of packages without a base.
}

// We currently create the PackageRevision, and then attach the resources
// TODO: Can we streamline this - create the package with its resources, or maybe return the draft?
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we address this by creating a new task type that could add the resources to the package as apart of creating the initial revision?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could, but I worry that it would make the model more complex, in that now some resources are directly created in PackageRevision. That said, we know that patches share some elements of this problem in the reclone-and-replay approach.

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.

2 participants