From 29c3628f51cffc46f7103a4dcb146af3cdf7d29a Mon Sep 17 00:00:00 2001 From: Andrew Benton Date: Tue, 12 Aug 2025 09:46:01 -0700 Subject: [PATCH] docs: use the correct admonition format --- docs/howto/overrides.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/howto/overrides.md b/docs/howto/overrides.md index f227ea041f..8cdcbde6a2 100644 --- a/docs/howto/overrides.md +++ b/docs/howto/overrides.md @@ -39,10 +39,11 @@ sql: go_type: "time.Time" ``` -.. tip:: +:::{tip} A single `db_type` override configuration applies to either nullable or non-nullable columns, but not both. If you want the same Go type to override regardless of nullability, you'll need to configure two overrides: one with `nullable: true` and one without. +::: ## The `overrides` list @@ -67,12 +68,15 @@ Each element in the `overrides` list has the following keys: Note that this only applies to `db_type` overrides and has no effect on `column` overrides. Defaults to `false`. -.. tip:: +:::{tip} A single `db_type` override configuration applies to either nullable or non-nullable columns, but not both. If you want the same Go type to override regardless of nullability, you'll need to configure two overrides: one with `nullable: true` and one without. +::: -.. note:: When generating code, `column` override configurations take precedence over `db_type` configurations. +:::{note} +When generating code, `column` override configurations take precedence over `db_type` configurations. +::: ### The `go_type` map