-
Notifications
You must be signed in to change notification settings - Fork 588
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
Remove lower-case restriction, lint. #522
Conversation
LGTM if I can get one more LGTM we can merge since this is strictly syntax/typo fixes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found one more typo in a part of the original spec, which has been touched by this PR. Apart from that, LGTM
spec.md
Outdated
All content attributes MUST be of scalar type (e.g. string, integer) | ||
that have a string-encoding defined. They MUST NOT be of complex type | ||
(e.g. structures, map). | ||
All content attributes MUST be of scalar type (e.g. string, integer) that have a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/content/context
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good eye!
@n3wscott want to get this one added to the PR?
rebase needed |
Signed-off-by: Scott Nichols <nicholss@google.com>
Signed-off-by: Doug Davis <dug@us.ibm.com>
ok - per Scott's request I rebased and made @deissnerk's s/content/context/ typo fix. Can I get one pair of eyes to review to make sure I didn't introduce another typo... then we can merge since it's just a minor typo type of PR? |
LGTM |
thanks @deissnerk |
Attribute names SHOULD begin with a lower-case letter
as it was redundant.