Remove warning about prop_or_else macro

The warning no longer applies to either version (next,
0.18.0).

website/docs/concepts/components/properties.md

@@ -37,11 +37,6 @@ For example, to default a boolean prop to `true`, use the attribute `#[prop_or(t
 
 Call `function` to initialize the prop value. `function` should have the signature `FnMut() -> T` where `T` is the field type.
 
-:::warning
-The function is currently called even if the prop is explicitly set. If your function is performance intensive, consider using `Option` where `None` values are initialized in the `create` method.
-See [#1623](https://github.com/yewstack/yew/issues/1623)
-:::
-
 ## PartialEq
 
 It makes sense to derive `PartialEq` on your props if you can do so.

website/versioned_docs/version-0.18.0/concepts/components/properties.md

@@ -37,11 +37,6 @@ For example, to default a boolean prop to `true`, use the attribute `#[prop_or(t
 
 Call `function` to initialize the prop value. `function` should have the signature `FnMut() -> T` where `T` is the field type.
 
-:::warning
-The function is currently called even if the prop is explicitly set. If your function is performance intensive, consider using `Option` where `None` values are initialized in the `create` method.
-See [#1623](https://github.com/yewstack/yew/issues/1623)
-:::
-
 ## PartialEq
 
 It makes sense to derive `PartialEq` on your props if you can do so.