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

Fix shorthand parser regressions in 1.8.0 #1473

Merged
merged 5 commits into from
Aug 31, 2015
Merged

Conversation

jamesls
Copy link
Member

@jamesls jamesls commented Aug 28, 2015

Fixes #1471 (unquoted values with spaces should be allowed).
Fixes #1470 (dash in key name should be allowed).

Added unit tests for these so we don't regress in the future.

cc @kyleknap @mtdowling @rayluo

Also makes the master regex more clear.
Fixes a reression in the new shorthand parser when
a value has spaces, e.g. `foo=with space`.  Only whitespace
within the value is allowed.  Trailing whitespace is still
trimmed.
Regression with the new shorthand parser.
@kyleknap
Copy link
Contributor

Change looks fine. Is there anything else that we need to take account for other than dashes like other symbol or unicode keys? Otherwise, 🚢

@jamesls
Copy link
Member Author

jamesls commented Aug 31, 2015

The key would correspond to valid names (not values) for AWS APIs. The only thing that I can think of that might affect this would be map names. I'll do some additional research on this.

@jamesls
Copy link
Member Author

jamesls commented Aug 31, 2015

Actually, DynamoDB's --items didn't previously qualify for shorthand because it is a nested map type, so it wasn't possible to use shorthand for put-item. I think we're good there.

@kyleknap
Copy link
Contributor

Ok cool. Should be good to merge then.

@jamesls jamesls merged commit 70e76e8 into aws:develop Aug 31, 2015
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

Successfully merging this pull request may close these issues.

2 participants