archive/pillar
0
0
Fork 0
Code Issues 42 Pull Requests Projects Releases Wiki Activity

Fix for {validate: markdown} when used in Eve

Browse Source 
Eve's Validator has not only a validate() function, but also
validate_update() and validate_replace(). Those set
self.persisted_document, so if that attribute exists we just use it.
This commit is contained in:
Sybren A. Stüvel
2018-07-13 17:13:26 +02:00
parent 8a0f582a80
commit 469f24d113
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
pillar/api/custom_field_validation.py
View File

@@ -180,6 +180,9 @@ class ValidateCustomFields(Validator):
""" """
# Find this field inside the original document # Find this field inside the original document
my_subdoc = self._subdoc_in_real_document() my_subdoc = self._subdoc_in_real_document()
if my_subdoc is None:
self._error(field, f'unable to find sub-document for path {self.document_path}')
return
save_to = pillar.markdown.cache_field_name(field) save_to = pillar.markdown.cache_field_name(field)
html = pillar.markdown.markdown(value) html = pillar.markdown.markdown(value)
@@ -190,7 +193,7 @@ class ValidateCustomFields(Validator):
This allows modification of the document being validated. This allows modification of the document being validated.
""" """
my_subdoc = self.__real_document my_subdoc = getattr(self, 'persisted_document') or self.__real_document
for item in self.document_path: for item in self.document_path:
my_subdoc = my_subdoc[item] my_subdoc = my_subdoc[item]
return my_subdoc return my_subdoc