You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: adr/2024-11-2-assertion-format.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ In 2020-12, we further refined this by offering two separate vocabularies, one t
23
23
24
24
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.)
25
25
26
-
Due to this consistency in user expectations have decided to:
26
+
Due to this consistency in user expectations, we have decided to:
27
27
28
28
1. make format an assertion keyword and strictly,
29
29
2. enforce it by moving the appropriate tests into the required section of the Test Suite.
0 commit comments