Skip to content

Add a way to configure the default multibase used #8889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
Jorropo opened this issue Apr 15, 2022 · 0 comments
Open
3 tasks done

Add a way to configure the default multibase used #8889

Jorropo opened this issue Apr 15, 2022 · 0 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@Jorropo
Copy link
Contributor

Jorropo commented Apr 15, 2022

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

After #8886.

We could configure what the default multibase is, for example myself I work mainly in the terminal and prefer base64url because it's shorter and pollute less of my screen.

I think the best way to do that would be an environment variable that the client read.
(there is no reason to force that config global to the node, however we don't have any client only config file and I don't think we need one).

Simply a simple:

export IPFS_DEFAULT_MULTIBASE=base256emoji

would be enough.

This flag would be used as default. If a command has a good reason to override it, such as ipfs cid format -b base32 for example, it would be ignored.

@Jorropo Jorropo added the kind/enhancement A net-new feature or improvement to an existing feature label Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

1 participant