Skip to content

explicit expression for '/' #1792

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
seiyab wants to merge 2 commits into from
Closed

explicit expression for '/' #1792

seiyab wants to merge 2 commits into from

Conversation

@seiyab
Copy link
Contributor

@seiyab seiyab commented Jan 2, 2019

before

The field name MUST begin with a slash.

after

The field name MUST begin with a `/`.

@MikeRalphson
Copy link
Member

MikeRalphson commented Jan 2, 2019

Thanks. Maybe we could say: "with a forward slash (/)". Also, changes which don't affect meaning or behaviour of the spec can go into the next patch release.

@seiyab seiyab mentioned this pull request Jan 2, 2019
Merged
@seiyab
Copy link
Contributor Author

seiyab commented Jan 2, 2019 •
edited
Loading

Thank you for your response.
So should I propose it like #1793 ?

@seiyab seiyab mentioned this pull request Jan 2, 2019
Closed
@MikeRalphson
Copy link
Member

MikeRalphson commented Jan 2, 2019

Yes #1793 looks great. Closing this as per your other issue (patch release changes will be forward-ported into v3.1.0 before release).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

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

@seiyab @MikeRalphson