upgrade to 1.0.35 and update changelog

Author: stevehu

CHANGELOG.md

@@ -9,6 +9,14 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 ### Changed
 
+## 1.0.35 - 2020-03-13
+
+### Added
+
+### Changed
+
+- fixes #272 Use ECMA-262 validator when requested. Thanks @eirnym
+
 ## 1.0.34 - 2020-03-12
 
 ### Added

README.md

@@ -80,15 +80,15 @@ Maven:
 <dependency>
     <groupId>com.networknt</groupId>
     <artifactId>json-schema-validator</artifactId>
-    <version>1.0.34</version>
+    <version>1.0.35</version>
 </dependency>
 ```
 
 Gradle:
 
 ```
 dependencies {
-    compile(group: "com.networknt", name: "json-schema-validator", version: "1.0.34");
+    compile(group: "com.networknt", name: "json-schema-validator", version: "1.0.35");
 }
 ```
 
@@ -112,6 +112,7 @@ For the latest version, please check the [release](https://github.com/networknt/
 
 ## [Collector Context](doc/collector_context.md)
 
+## [ECMA-262 Regex](doc/ecma-262.md)
 
 ## Known issues
 

doc/ecma-262.md

@@ -0,0 +1,29 @@
+For the pattern validator, we now have two options for regex in the library. The default one is java.util. regex; however, you can use the ECMA-262 standard library org.jruby.joni by configuration. 
+
+As we know, the JSON schema is designed based on the Javascript language and its regex. The Java internal implementation has some differences which don't comply with the standard. For most users, these edge cases are not the issue as they are not using them anyway. Even when they are using it, they are expecting the Java regex result as the application is built on the Java platform. For users who want to ensure that they are using 100% standard patter validator, we have provided an option to override the default regex library with org.jruby.joni that is complying with the ECMA-262 standard.
+
+### Which one to choose?
+
+If you want a faster regex lib and don't care about the slight difference between Java and Javascript regex, then you don't need to do anything. The default regex lib is the java.util.regex.
+
+If you want to ensure full compliance, use the org.jruby.joni. It is 1.5 times slower then java.util.regex. Depending on your use case, it might not be an issue. 
+
+### How to switch?
+
+Here is the test case that shows how to pass a config object to use the ECMA-262 library.
+
+```
+    @Test(expected = JsonSchemaException.class)
+    public void testInvalidPatternPropertiesValidatorECMA262() throws Exception {
+        SchemaValidatorsConfig config = new SchemaValidatorsConfig();
+        config.setEcma262Validator(true);
+        JsonSchemaFactory factory = JsonSchemaFactory.getInstance(SpecVersion.VersionFlag.V4);
+        JsonSchema schema = factory.getSchema("{\"patternProperties\":6}", config);
+
+        JsonNode node = getJsonNodeFromStringContent("");
+        Set<ValidationMessage> errors = schema.validate(node);
+        Assert.assertEquals(errors.size(), 0);
+    }
+```
+
+

pom.xml

@@ -20,7 +20,7 @@
     <modelVersion>4.0.0</modelVersion>
     <groupId>com.networknt</groupId>
     <artifactId>json-schema-validator</artifactId>
-    <version>1.0.34</version>
+    <version>1.0.35</version>
     <packaging>bundle</packaging>
     <description>A json schema validator that supports draft v4, v6, v7 and v2019-09</description>
     <url>https://github.com/networknt/json-schema-validator</url>