summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJulian Berman <Julian@GrayVines.com>2013-05-26 22:12:18 -0400
committerJulian Berman <Julian@GrayVines.com>2013-05-26 22:12:18 -0400
commited51bcec6af43a4647bbb24f6ea41f8e7f7a67b7 (patch)
tree4b061239634cb6324736af7b78bbb92f5805ec96 /docs
parent93467f114cb7013a8a623ac177834f9c13676e31 (diff)
downloadjsonschema-ed51bcec6af43a4647bbb24f6ea41f8e7f7a67b7.tar.gz
Add a FAQ with info on default.
Diffstat (limited to 'docs')
-rw-r--r--docs/faq.rst48
-rw-r--r--docs/index.rst1
2 files changed, 49 insertions, 0 deletions
diff --git a/docs/faq.rst b/docs/faq.rst
new file mode 100644
index 0000000..97a53d7
--- /dev/null
+++ b/docs/faq.rst
@@ -0,0 +1,48 @@
+==========================
+Frequently Asked Questions
+==========================
+
+**Why doesn't my schema that has a :validator:`default` property actually set
+the default on my instance?**
+
+The basic answer is that the specification does not require that
+:validator:`default` actually do anything.
+
+For an inkling as to *why* it doesn't actually do anything, consider that none
+of the other validators modify the instance either. More importantly, having
+:validator:`default` modify the instance can produce quite peculiar things.
+It's perfectly valid (and perhaps even useful) to have a default that is not
+valid under the schema it lives in! So an instance modified by the default
+would pass validation the first time, but fail the second!
+
+Still, filling in defaults is a thing that is useful. :mod:`jsonschema` allows
+you to :doc:`define your own validators <creating>`, so you can easily create a
+:class:`IValidator` that does do default setting. Here's some code to get you
+started:
+
+ .. code-block:: python
+
+ from jsonschema import Draft4Validator, validators
+
+
+ def set_defaults(validator, properties, instance, schema):
+ Draft4Validator.VALIDATORS["properties"](
+ validator, properties, instance, schema,
+ )
+ for property, subschema in properties.iteritems():
+ if "default" in subschema:
+ instance.setdefault(property, subschema["default"])
+
+
+ DefaultValidatingDraft4Validator = validators.extend(
+ Draft4Validator, {"properties" : set_defaults},
+ )
+
+See the above-linked document for more info on how this works, but basically,
+it just extends the :validator:`properties` validator on a
+:class:`Draft4Validator` to then go ahed and update all the defaults.
+
+If you're interested in a more interesting solution to a larger class of these
+types of transformations, keep an eye on `Seep
+<https://github.com/Julian/Seep>`_, which is an experimental data
+transformation and extraction library written on top of :mod:`jsonschema`.
diff --git a/docs/index.rst b/docs/index.rst
index 6c3c9cf..96a09e2 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -42,6 +42,7 @@ Contents:
errors
references
creating
+ faq
Indices and tables