This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new b83a33877 Mention difference of handling null values in
RESOURCERESOLVER_MOCK
b83a33877 is described below
commit b83a33877b98ad64b20f0884325687bf24ec2a99
Author: Konrad Windszus <[email protected]>
AuthorDate: Thu Jul 31 15:46:25 2025 +0200
Mention difference of handling null values in RESOURCERESOLVER_MOCK
---
src/main/jbake/content/documentation/development/sling-mock.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/main/jbake/content/documentation/development/sling-mock.md
b/src/main/jbake/content/documentation/development/sling-mock.md
index aafcbd3e9..a9f92a03c 100644
--- a/src/main/jbake/content/documentation/development/sling-mock.md
+++ b/src/main/jbake/content/documentation/development/sling-mock.md
@@ -167,7 +167,7 @@ Resource resolver types currently supported:
* Simulates an In-Memory resource tree, does not provide adaptions to JCR API.
* Based on the [Sling resourceresolver-mock
implementation][resourceresolver-mock] implementation.
* You can use it to make sure the code you want to test does not contain
references to JCR API.
-* Behaves slightly different from JCR resource mapping e.g. handling binary
and date values.
+* Behaves slightly different from JCR resource mapping e.g. with respect to
handling binary, date and null values.
* This resource resolver type is very fast because data is stored in memory
and no JCR mapping is applied.
**RESOURCEPROVIDER_MOCK**
