mirror of
https://github.com/ansible-collections/community.crypto.git
synced 2026-03-26 21:33:25 +00:00
Add type hints and type checking (#885)
* Enable basic type checking. * Fix first errors. * Add changelog fragment. * Add types to module_utils and plugin_utils (without module backends). * Add typing hints for acme_* modules. * Add typing to X.509 certificate modules, and add more helpers. * Add typing to remaining module backends. * Add typing for action, filter, and lookup plugins. * Bump ansible-core 2.19 beta requirement for typing. * Add more typing definitions. * Add typing to some unit tests.
This commit is contained in:
@@ -5,3 +5,4 @@ minor_changes:
|
||||
- "Python code modernization: remove Python 3 specific code (https://github.com/ansible-collections/community.crypto/pull/877)."
|
||||
- "Python code modernization: avoid unnecessary string conversion (https://github.com/ansible-collections/community.crypto/pull/880)."
|
||||
- "Python code modernization: avoid using ``six`` (https://github.com/ansible-collections/community.crypto/pull/884)."
|
||||
- "Python code modernization: add type hints and type checking (https://github.com/ansible-collections/community.crypto/pull/885)."
|
||||
|
||||
5
changelogs/fragments/relative-timestamps.yml
Normal file
5
changelogs/fragments/relative-timestamps.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
breaking_changes:
|
||||
- "The validation for relative timestamps is now more strict. A string starting with ``+`` or ``-`` must be valid,
|
||||
otherwise validation will fail. In the past such strings were often silently ignored, and in many cases the code
|
||||
which triggered the validation was not able to handle no result
|
||||
(https://github.com/ansible-collections/community.crypto/pull/885)."
|
||||
Reference in New Issue
Block a user