docs(readme): complex compound types are properly handled (#38)

Author: lucsorel

README.md

@@ -197,6 +197,7 @@ poetry run pytest -v --cov=py2puml --cov-branch --cov-report term-missing --cov-
 
 # Changelog
 
+* `0.7.1`: removed obsolete part of documentation: deeply compound types are now well handled (by version `0.7.0`)
 * `0.7.0`: improved the generated PlantUML documentation (added the namespace structure of the code base, homogenized type  between inspection and parsing), improved relationships management (handle forward references, deduplicate relationships)
 * `0.6.1`: handle class names with digits
 * `0.6.0`: handle abstract classes
@@ -233,10 +234,6 @@ Follow the [contributing guide](CONTRIBUTING.md).
 
   > The Python runtime does not enforce function and variable type annotations. They can be used by third party tools such as type checkers, IDEs, linters, etc.
 
-  * complex type hints with more than one level of genericity are not properly handled for the moment: `List[MyClass]` or `Dict[str, MyClass]` are handled properly, `Dict[str, List[MyClass]]` is not.
-  If your domain classes (also called business objects or DTOs) have attributes with complex type hints, it may be a code smell indicating that you should write a class which would better represent the business logic.
-  But I may improve this part of the library as well 😀
-
 * regarding the detection of instance attributes with **AST parsing**:
   * only constructors are visited, attributes assigned in other functions won't be documented
   * attribute types are inferred from type annotations: