Skip to content

rename namespace ID to namespace #172

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.

Sign up for GitHub

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

Jump to bottom
Closed
rach-id opened this issue Aug 8, 2023 · 0 comments · Fixed by #175
Closed

rename namespace ID to namespace #172

rach-id opened this issue Aug 8, 2023 · 0 comments · Fixed by #175
Assignees
@rach-id
Labels
contracts

Comments

@rach-id
Copy link
Member

rach-id commented Aug 8, 2023 

          [optional] in a separate PR it may make sense to rename namespace ID to namespace for similar reasons to https://github.com/celestiaorg/nmt/issues/206

Originally posted by @rootulp in #171 (comment)
@rach-id rach-id self-assigned this Aug 8, 2023
@rach-id rach-id added this to core/app Aug 8, 2023
@rach-id rach-id moved this to Backlog in core/app Aug 8, 2023
@rach-id rach-id mentioned this issue Aug 8, 2023
Merged
5 tasks
@rach-id rach-id moved this from Backlog to In Progress in core/app Aug 11, 2023
@rach-id rach-id mentioned this issue Aug 12, 2023
Merged
5 tasks
@rach-id rach-id moved this from In Progress to In Review in core/app Aug 12, 2023
rach-id added a commit that referenced this issue Sep 8, 2023
@rach-id @rootulp
feat!: use a struct for namespace and rename namespaceID (#175)
eb7a4e7 
<!--
Please read and fill out this form before submitting your PR.

Please make sure you have reviewed our contributors guide before
submitting your
first PR.
-->

## Overview

<!-- 
Please provide an explanation of the PR, including the appropriate
context,
background, goal, and rationale. If there is an issue with this
information,
please provide a tl;dr and link the issue. 
-->

Closes #172
and #174


## Checklist

<!-- 
Please complete the checklist to ensure that the PR is ready to be
reviewed.

IMPORTANT:
PRs should be left in Draft until the below checklist is completed.
-->

- [ ] New and updated code has appropriate documentation
- [ ] New and updated code has new and/or updated testing
- [ ] Required CI checks are passing
- [ ] Visual proof for any user facing features like CLI or
documentation updates
- [ ] Linked issues closed with keywords

---------

Co-authored-by: Rootul P <[email protected]>
@github-project-automation github-project-automation bot moved this from In Review to Done in core/app Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rach-id rach-id

Labels
contracts
Projects
core/app
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat!: use a struct for namespace and rename namespaceID rach-id/quantum-gravity-bridge
1 participant
@rach-id