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

CIP-0119 | Add "@" to the "@type" field of "references" #950

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

palas
Copy link

@palas palas commented Dec 16, 2024

This PR addresses the issue #945, by adding an @ symbol at the beginning of name of the @type field of the references field of CIP-0119, updating it in the JSON schema and the README.md.

Fixes #945.

@palas palas changed the title Add "@" to the "@type" field of "reference" (address #945) CIP-0119 | Add "@" to the "@type" field of "reference" (address #945) Dec 16, 2024
@rphair rphair changed the title CIP-0119 | Add "@" to the "@type" field of "reference" (address #945) CIP-0119 | Add "@" to the "@type" field of "reference" Dec 16, 2024
@rphair rphair added the Category: Metadata Proposals belonging to the 'Metadata' category. label Dec 16, 2024
Copy link
Collaborator

@rphair rphair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks complete from my (non-implementor) level but please @Ryun1 @Crypto2099 @perturbing post if there are lurking implications of this change.

Thanks @gitmachtl for confirming in #945 (comment) that this should be OK but also perhaps that db-sync is an application to watch out for.

@rphair rphair added Update Adds content or significantly reworks an existing proposal State: Last Check Review favourable with disputes resolved; staged for merging. labels Dec 16, 2024
@palas palas changed the title CIP-0119 | Add "@" to the "@type" field of "reference" CIP-0119 | Add "@" to the "@type" field of "references" Dec 17, 2024
@Ryun1
Copy link
Collaborator

Ryun1 commented Dec 18, 2024

Great spot @palas
ill reach out to tooling to double check that this change wouldnt break their implementations before we merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Metadata Proposals belonging to the 'Metadata' category. State: Last Check Review favourable with disputes resolved; staged for merging. Update Adds content or significantly reworks an existing proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CIP-0119 - Inconsistent field name
3 participants