Skip to content
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

feat!: move space register email parameter to an --email option and add --provider option #60

Merged
merged 3 commits into from
Mar 23, 2023

Conversation

travis
Copy link
Member

@travis travis commented Mar 22, 2023

If we're only authorized to act as a single account we shouldn't need to pass an email address to space register since we can infer which one to use from the delegations we currently have.

Preserve the ability to pass email using the --email option for cases where we are authorized as multiple accounts.

Also add a --provider option to space register to allow users to register spaces with other providers like NFT.Storage.

If we're only authorized to act as a single account we shouldn't need to pass an email address to `space register` since we can infer which one to use from the delegations we currently have.

Preserve the ability to pass email for cases where we are authorized as multiple accounts.
this will allow us to register spaces with NFT.storage
@travis travis changed the title feat: make email parameter to space register optional feat: make email parameter to space register optional and add --provider option Mar 22, 2023
README.md Outdated Show resolved Hide resolved
index.js Show resolved Hide resolved
index.js Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
index.js Show resolved Hide resolved
@alanshaw
Copy link
Member

could do with tests...

@travis
Copy link
Member Author

travis commented Mar 22, 2023

could do with tests...

Yep agreed - I didn't see any existing tests for this so wanted to get this up before I go down that rabbithole, but will look at writing tests for this now...

@travis travis changed the title feat: make email parameter to space register optional and add --provider option feat: move email parameter to space register to an --email option and add --provider option Mar 22, 2023
@travis travis changed the title feat: move email parameter to space register to an --email option and add --provider option feat!: move email parameter to space register to an --email option and add --provider option Mar 22, 2023
@travis travis changed the title feat!: move email parameter to space register to an --email option and add --provider option feat!: move space register email parameter to an --email option and add --provider option Mar 22, 2023
@travis
Copy link
Member Author

travis commented Mar 23, 2023

ok I've opened an issue for testing after digging in a bit - we need to figure out how to test this and other commands that depend on remote services: #61

@travis travis merged commit c1ed0e5 into main Mar 23, 2023
@travis travis deleted the feat/register-space-email-optional branch March 23, 2023 00:07
olizilla pushed a commit that referenced this pull request Mar 23, 2023
🤖 I have created a release *beep* *boop*
---


##
[2.0.0](v1.2.2...v2.0.0)
(2023-03-23)


### ⚠ BREAKING CHANGES

* upgrade to latest access & upload clients
([#64](#64))
* move `space register` email parameter to an `--email` option and add
`--provider` option
([#60](#60))
* use new account model
([#53](#53))

### Features

* move `space register` email parameter to an `--email` option and add
`--provider` option
([#60](#60))
([c1ed0e5](c1ed0e5))
* show help text if no cmd
([#63](#63))
([fd5f342](fd5f342))
* update README with new ToS
([#62](#62))
([4ce61d7](4ce61d7)),
closes [#54](#54)
* upgrade to latest access & upload clients
([#64](#64))
([b5851ca](b5851ca))
* use new account model
([#53](#53))
([7f63286](7f63286))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

3 participants