Enhance README advice on OpenAPI type usage

Clarify the importance of using named types in OpenAPI schemas for better code generation.

Author: davidmoten

README.md

@@ -134,7 +134,7 @@ Here's an example showing more configuration options:
 
 ## General advice
 * Prefer yaml definitions to json, much easier to read and to hold comments
-* As much as possible make sure you put your types in the `#/components/schemas` section of your openapi yaml/json file (use `$ref`!). The same goes for responses, pathItems, and anything else that can be referred to with a `$ref`. Don't use anonymous types, it makes for an ugly experience with generated code.
+* As much as possible make sure you put your types in the `#/components/schemas` section of your openapi yaml/json file (use `$ref`!). The same goes for responses, pathItems, and anything else that can be referred to with a `$ref`. Don't use anonymous types, it makes for an ugly experience with generated code (and hinders reuse).
 * avoid using complex parameters, use json request bodies instead (Spring Boot for example doesn't have annotation support for many parameter strategies)
 * Specify `format: int32` on integers to ensure you end up with `int/integer` types in generated code
 * Be sure to specify the properties that are mandatory (using `required:`)