Skip to content

RFC4912 required a <type> for a named type that defines a type #93

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
Merged
merged 1 commit into from
Jul 13, 2020
Merged

RFC4912 required a <type> for a named type that defines a type #93

merged 1 commit into from
Jul 13, 2020

Conversation

SmartLayer
Copy link

@SmartLayer SmartLayer commented Jun 25, 2020 •
edited
Loading

  1. merge this together with RFC4912 required a <type> for a named type that defines a type TokenScript#365

  2. Don't merge this in until both αW can handle the new schema.

@SmartLayer SmartLayer mentioned this pull request Jun 25, 2020
Merged
This was referenced Jun 25, 2020
Merged
Merged
@JamesANZ JamesANZ merged commit ee55057 into master Jul 13, 2020
@JamesANZ JamesANZ deleted the correct-violation-of-rfc4912 branch July 13, 2020 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JamesANZ JamesANZ JamesANZ approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@SmartLayer @JamesANZ