Jira (NPUP-43) Missing a colon after a resource title causes confusing error message

[Peter Huene (JIRA)]

Title: Message Title

Peter Huene created an issue   Native Puppet / NPUP-43 Missing a colon after a resource title causes confusing error message Issue Type: Bug Affects Versions: NPUP 0.1.0 Assignee: Peter Huene Created: 2016/05/10 2:04 PM Priority: Normal Reporter: Peter Huene The following: file { foo } Results in this error message: Error: test.pp:3:1: expected '=>' but found '}'. } ^ Which is confusing. This is due to the fact that the resource _expression_ rule fails to match, and the parser instead matches the string rule and then attempts to match the hash rule, which has an expectation point following the key _expression_ (hence => is expected). The expected error should be: Error: test.pp:3:1: expected ':' but found '}'. } ^ This should be possible as the compiler can tell that the resource body rule should be able to expect a colon (provided the token is not => due to other rules having the same syntax). Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.