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

no error on wildcard expected but undefined ?! #54

Closed
andreineculau opened this issue Dec 15, 2016 · 1 comment
Closed

no error on wildcard expected but undefined ?! #54

andreineculau opened this issue Dec 15, 2016 · 1 comment
Assignees

Comments

@andreineculau
Copy link
Member

it seems strange, and potentially a bug that

{
  "foo": "{{_}}",
  "{{_}}": "{{unexpected}}"
}

will not fail if the payload is actually the empty object {}

@andreineculau andreineculau self-assigned this Jan 5, 2017
@andreineculau andreineculau added this to the 1.6.0 milestone Jan 5, 2017
@andreineculau
Copy link
Member Author

seems like a breaking change was not identified in the 1.3.0 release
c661b85 allow {{_}} to match nothing

this means that a new keyword {{expected}} needs to be added if one wants to require a value

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

No branches or pull requests

1 participant