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

refactor: rename record fields #1987

Closed
wants to merge 13 commits into from

Conversation

shumkov
Copy link
Member

@shumkov shumkov commented Jul 23, 2024

Issue being fixed or feature implemented

According to the original idea, DPNS can resolve information from any services or network (not just located in dash network), including IPFS, various identity services, etc. Also we have naming convention to use Id postfix in case if we pointing to identifier.

What was done?

  • Renamed records.identity to records.dashIdentityId

How Has This Been Tested?

Updated existing tests

Breaking Changes

None

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@shumkov shumkov requested a review from QuantumExplorer as a code owner July 23, 2024 08:56
@QuantumExplorer
Copy link
Member

The record you are looking at is for an identity, not an identityId. While the underlying item is represented by an identityId it's not common practice to name the underlying representation but instead name the business logic item. This is the case in DNS and ENS.

As for DashIdentity vs Identity, common practice in the industry has been to not prefix with your own blockchain. This makes things cheaper for our users as the records are slightly smaller.

Base automatically changed from fix/UniqueContestedResourceFix to v1.0-dev July 23, 2024 13:50
@shumkov shumkov closed this Jul 23, 2024
@shumkov shumkov deleted the fix/UniqueContestedResourceFix-2 branch July 23, 2024 14:04
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.

2 participants