Skip to content

Commit c91ccda

Browse files
committed
Merge branch 'hotfix/1.0.5'
2 parents f1547c5 + 1b9b886 commit c91ccda

File tree

2 files changed

+15
-13
lines changed

2 files changed

+15
-13
lines changed

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1.0.4
1+
1.0.5

src/input-validation/validation.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -140,26 +140,28 @@ _Post-validation Actions_ should also be performed.
140140
The _Post-validation Actions_ used vary with the context and are divided in
141141
three separate categories:
142142

143-
## Enforcement Actions
143+
* **Enforcement Actions**
144144

145-
Several types of _Enforcement Actions_ exist in order to better secure our
146-
application and data.
145+
Several types of _Enforcement Actions_ exist in order to better secure our
146+
application and data.
147147

148-
One type of _Enforcement Action_ consists in informing the user that the
149-
submitted data has failed to comply with the requirements, and that the data
150-
should be modified in order to comply with the required conditions.
148+
* inform the user that submitted data has failed to comply with the
149+
requirements and therefor the data should be modified in order to comply
150+
with the required conditions.
151151

152-
Another type of enforcement can be made by modifying the user submitted data
153-
on the server side without notifying the user of said changes. This is most
154-
suitable in systems with interactive usage.
152+
* modify user submitted data on the server side without notifying the user of
153+
said changes. This is most suitable in systems with interactive usage.
155154

156-
**Note:** The latter is used mostly in cosmetic changes (modifying sensitive
155+
**Note:** The latter is used mostly in cosmetic changes (modifying sensitive
157156
user data can lead to problems like truncating, which incur in data loss).
157+
* **Advisory Action**
158158

159-
* **Advisory Action** - Advisory Actions usually allow for unchanged data
159+
Advisory Actions usually allow for unchanged data
160160
to be entered, but the source actor is informed that there were issues with
161161
said data. This is most suitable for non-interactive systems.
162-
* **Verification Action** - Verification Action refer to special cases in
162+
* **Verification Action**
163+
164+
Verification Action refer to special cases in
163165
Advisory Actions. In these cases, the user submits the data and the source
164166
actor asks the user to verify said data and suggests changes. The user then
165167
accepts these changes or keeps his original input.

0 commit comments

Comments
 (0)