[unomi] branch UNOMI-778-remove-uselss-unevaluated-property updated: UNOMI-778 : update documentation

[js...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jsinovassinnaik pushed a commit to branch UNOMI-778-remove-uselss-unevaluated-property
in repository https://gitbox.apache.org/repos/asf/unomi.git


The following commit(s) were added to refs/heads/UNOMI-778-remove-uselss-unevaluated-property by this push:
     new c4fbf0e91 UNOMI-778 : update documentation
c4fbf0e91 is described below

commit c4fbf0e9166fe682ef72516ae0b517a2bb2f90dc
Author: jsinovassin <js...@jahia.com>
AuthorDate: Tue May 9 16:53:01 2023 +0200

    UNOMI-778 : update documentation
---
 manual/src/main/asciidoc/jsonSchema/introduction.adoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/manual/src/main/asciidoc/jsonSchema/introduction.adoc b/manual/src/main/asciidoc/jsonSchema/introduction.adoc
index e77d5ed4d..d9755b12f 100644
--- a/manual/src/main/asciidoc/jsonSchema/introduction.adoc
+++ b/manual/src/main/asciidoc/jsonSchema/introduction.adoc
@@ -184,6 +184,7 @@ The *unevaluatedProperties* keyword is useful for schema composition as well as
 This keyword is similar to *additionalProperties* except that it can recognize properties declared in sub schemas.
 When setting the *unevaluatedProperties* value to *false*, the properties which are not present in the properties part and are not present in the sub schemas will be considered as invalid.
 
+The *unevaluatedProperties* keyword should only be set on the root schema. Otherwise it could leads to less readable messages when validating events.
 Example with the following schema:
 
 [source]