sup icon indicating copy to clipboard operation
sup copied to clipboard

Add feature: naming and renaming

Open Swader opened this issue 5 years ago • 2 comments

When starting a new project, sup should ask about the name, version, creator, license, etc. These values should be filled into Cargo.toml inside both runtime and node folder.

Likewise, an existing project should be rename-able with a simple command using this package manager. Something like sup rename foo should rename the bar project by replacing all invocations of bar with foo.

Swader avatar Oct 16 '20 14:10 Swader

Sorry for the late~

When starting a new project, sup should ask about the name, version, creator, license, etc. These values should be filled into Cargo.toml inside both runtime and node folder.

Step-1

Here will be a ~/.sup/config.toml to handle this, it would be like:

[node]
registry = ""
authors = ["", ""]
license = ["", ""]

These will overwrite the matched info in crates in runtime and node.

Step-2

A set command, for example, we can run

$ sup set --version <version> --path <node-path>

to overwrite all versions.


Likewise, an existing project should be rename-able with a simple command using this package manager. Something like sup rename foo should rename the bar project by replacing all invocations of bar with foo.

This rename command is awesome as well, I'll implement it~


Thanks for your advice!!! The upgrade process will link to this issue~

clearloop avatar Oct 18 '20 03:10 clearloop

Likewise, an existing project should be rename-able with a simple command using this package manager. Something like sup rename foo should rename the bar project by replacing all invocations of bar with foo.

This can be implemented but it is not a substrate registry operation, it's about cargo, wondering if it will make sup too complex?

clearloop avatar Nov 21 '20 20:11 clearloop