Skip to content
This repository has been archived by the owner on Jul 11, 2019. It is now read-only.

Re-use deployed implementations from previous version if unchanged #94

Open
spalladino opened this issue May 11, 2018 · 1 comment
Open
Labels
kind:enhancement An upgrade or a new feature that improves the system topic:tools Off-chain tooling in general
Milestone

Comments

@spalladino
Copy link
Contributor

When creating a new-version for an app, all its contracts are re-uploaded, and registered in the version's contracts directory. As an optimization, if a contract was unmodified between the two versions, instead of re-uploading, register the already deployed instance in the new contracts directory.

@spalladino spalladino added kind:enhancement An upgrade or a new feature that improves the system topic:tools Off-chain tooling in general labels May 11, 2018
@spalladino spalladino added this to the v0.2.0 milestone May 11, 2018
@facuspagnuolo facuspagnuolo modified the milestones: Backlog, MVP, Sprint #2, Sprint #1, v2.0.0 Jun 4, 2018
@spalladino
Copy link
Contributor Author

This becomes more important when developing large libraries, where if a patch needs to be released, only a single contract should be uploaded, instead of all contracts in the project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind:enhancement An upgrade or a new feature that improves the system topic:tools Off-chain tooling in general
Projects
None yet
Development

No branches or pull requests

3 participants