Fix code annotation in @computed_field documentation (#11693)

Viicos · web-flow · commit 4a8c92970525 · 2025-04-08T14:58:26.000+02:00
diff --git a/docs/concepts/fields.md b/docs/concepts/fields.md
@@ -937,6 +937,10 @@ print(Box.model_json_schema(mode='serialization'))
 """
 ```
 
+1. If not specified, [`computed_field`][pydantic.fields.computed_field] will implicitly convert the method
+   to a [`property`][]. However, it is preferable to explicitly use the [`@property`][property] decorator
+   for type checking purposes.
+
 Here's an example using the `model_dump` method with a computed field:
 
 ```python
@@ -949,7 +953,7 @@ class Box(BaseModel):
     depth: float
 
     @computed_field
-    @property  # (1)!
+    @property
     def volume(self) -> float:
         return self.width * self.height * self.depth
 
@@ -959,10 +963,6 @@ print(b.model_dump())
 #> {'width': 1.0, 'height': 2.0, 'depth': 3.0, 'volume': 6.0}
 ```
 
-1. If not specified, [`computed_field`][pydantic.fields.computed_field] will implicitly convert the method
-   to a [`property`][]. However, it is preferable to explicitly use the [`@property`][property] decorator
-   for type checking purposes.
-
 As with regular fields, computed fields can be marked as being deprecated:
 
 ```python
