Skip to content

Commit 81d64ba

Browse files
Update adr/2024-11-2-assertion-format.md
Co-authored-by: Jason Desrosiers <jdesrosi@gmail.com>
1 parent e13e156 commit 81d64ba

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

adr/2024-11-2-assertion-format.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ In 2020-12, we further refined this by offering two separate vocabularies, one t
2323

2424
However, the fact remains that our users consistently report (via questions in Slack, GitHub, and StackOverflow) that they expect format to validate. (The most recent case I can think of was only last week, in .Net's effort to build a short-term solution for schema generation from types.)
2525

26-
Due to this consistency in user expectations have decided to:
26+
Due to this consistency in user expectations, we have decided to:
2727

2828
1. make format an assertion keyword and strictly,
2929
2. enforce it by moving the appropriate tests into the required section of the Test Suite.

0 commit comments

Comments
 (0)