Please check if the PR fulfills these requirements
[x] I have read the CONTRIBUTING guidelines
[x] A new item has been added to NEWS.md
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Internal refactoring
Improved error messages and user interface
What is the current behavior? (You can also link to an open issue here)
There is an unnecessary nesting with validate_types() looping over an internal validate_type()
The error message is not helpful enough in the case of multiple tags with incorrect types
What is the new behavior (if this is a feature change)?
validate_types() now contains all the functionality and is no longer a wrapper around the very simple validate_type() internal function
The error message now returns all tags with incorrect types during the first call.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
The error message is updated and this could break workflows relying on capturing an exact message but this should not happen anyways (see #90 for a better approach).
Please check if the PR fulfills these requirements
[x] I have read the CONTRIBUTING guidelines
[x] A new item has been added to
NEWS.md[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Internal refactoring
Improved error messages and user interface
What is the current behavior? (You can also link to an open issue here)
There is an unnecessary nesting with
validate_types()looping over an internalvalidate_type()The error message is not helpful enough in the case of multiple tags with incorrect types
What is the new behavior (if this is a feature change)?
validate_types()now contains all the functionality and is no longer a wrapper around the very simplevalidate_type()internal functionThe error message now returns all tags with incorrect types during the first call.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
The error message is updated and this could break workflows relying on capturing an exact message but this should not happen anyways (see #90 for a better approach).
Related to #105