Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Chain naming consistency for collectives #2699

Open
stakeworld opened this issue Jun 7, 2023 · 1 comment
Open

Chain naming consistency for collectives #2699

stakeworld opened this issue Jun 7, 2023 · 1 comment
Labels
I4-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.

Comments

@stakeworld
Copy link

stakeworld commented Jun 7, 2023

Not really a bug but more an inconsistency which can be frustrating in automatic scripting: for all chains the used --chain name is consistent with naming of the database on disk but not for collectives-polkadot, which uses an _ in the database directory.

For example --chain polkadot creates <basedir>/chains/polkadot, --chain bridge-hub-kusamacreates <basedir>/chain/bridge-hub-kusama etc.

Only --chain collectives-polkadot creates <basedir>/chains/collectives_polkadot (with an underscore). I would think it preferable to keep a consistent naming scheme?

@joepetrowski joepetrowski added the I4-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue. label Jul 18, 2023
@joepetrowski
Copy link
Contributor

Agreed, change is simple (here), but obviously breaking for node operators or will require a renaming like for the Statemint path.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
I4-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

2 participants