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

supportedstandards in NEP-15 should incorporate NEP-10 formatting detail #139

Open
hal0x2328 opened this issue Jul 4, 2021 · 0 comments

Comments

@hal0x2328
Copy link
Contributor

hal0x2328 commented Jul 4, 2021

Since NEP-10 was marked obsolete once the SupportedStandards was moved to the manifest, there is no current NEP I can find that specifies how the name and number of the NEP should be formatted.

NEP-10 was specific in saying The return values {"nep-5"}, {"NEP5"}, and {"nep5"} will generally be considered invalid responses unless "nep5", for example, is a valid code for a specification in a non-NEP specification system.

NEP-15 does say The supportedstandards field describes the NEP-10 values. but now that NEP-10 is obsolete, maybe the formatting guidelines should be moved into NEP-15.

@hal0x2328 hal0x2328 changed the title supportedstandards in manifest should still follow NEP-10 formatting supportedstandards in NEP-15 should incorporate NEP-10 formatting detail Jul 4, 2021
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

No branches or pull requests

1 participant