Skip to content

Commit 5f2932c

Browse files
twofbenjie
andauthored
Update src/pages/blog/2024-08-14-semantic-nullability-for-application-developers.mdx
Co-authored-by: Benjie <[email protected]>
1 parent b855d11 commit 5f2932c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/pages/blog/2024-08-14-semantic-nullability-for-application-developers.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,6 @@ Because your client can decide how it handles errors, it will also be responsibl
8888

8989
![Example code generation](https://i.imgur.com/i3hdCND.png)
9090

91-
You should use the modified version of the schema when doing code generation for your frontend application.
91+
The modified version of the schema can also incorporate any client-side schema extensions you may have. You should use the modified version of the schema when doing code generation for your frontend application.
9292

9393
Altering the error handling behavior of your client may be a breaking change if your schema has already adopted semantic nullability, so it's suggested that you select new error handling behavior for your client first. Read the documentation for your specific client for more information.

0 commit comments

Comments
 (0)