Failure Reporting Improvements

This release removes some of the verbosity in the failure reports, and moves them back to using strict stack levels.

Optional Member and Unordered Array Bug Fixes

• Fixed bug with optional object members passing if their values were incorrect
• Fixed bug with unordered arrays that caused the evaluation to read past the end

Bug fixes and Enhancements to 0.8.0

• Various issues with stack traces at the command line instead of proper errors
• --process-parts now takes an optional directory
• --process-parts now creates an XML entity reference file snippet
• override rules can now reference rules in the original ruleset
• more readable failure report
• more readable verbose messages
• @{not} annotation on targer rules were not honored but now fixed
• better checking for groups referenced from arrays and objects

Adds --process-parts Option

This release adds the --process-parts option.

The --process-parts option extracts parts of a JCR file into multiple files based
on comments in the file. It can also create a new file without the
comments. This is useful for JCR going into specification documents
where it is nice to break the JCR up for illustrative purposes in
the specification but to also have one JCR file for programmatic
testing purposes.

The file parts are extracted using the comments

; start_part FILENAME

and

; end_part

The comments must also be the only thing present on the line
though leading whitespace is allowed if desired.

To get a new file with all parts but these comments, use this

; all_parts FILENAME

0.7.0: Tracks draft -09

• Tracks the -09 draft
• Fixes to allow annotations for groups in arrays and objects
• Text output is now proper JCR
• Fixed issue with multiple files on the command line with MacOS
• Support for Ruby 2.4
• Dropped Ruby 1.8, 1.9, and 2.0. CI testing on:
  • Linux 2.1, 2.3, 2.4, and JRuby 9.1
  • OSX 2.3 and 2.4
• Fixes to ABNF in multi-line directives
• Much better CLI and programmatic validation failure information and structures
• Fixes to print errors when the JCR fails to parse

First release that tracks -07

This is the first release that tracks the -07 IETF draft.
That draft can be found here: https://raw.githubusercontent.com/arineng/jcr/07/draft-newton-json-content-rules.txt

0.5.3

Fix to gemspec so that dependencies are added.

Minor Tweaks

• Added -J command line option
• Changed command line option -s to -S to be more consistent
• Will no longer allow member rules to be root rules
• More group rule checking (code was there, just wan't being invoked)

First Public Beta

Merge pull request #55 from codalogic/ruby-abnf-extracter

Ruby ABNF extracter