Jsonargparse

--------------------

Fixed
^^^^^
- AST resolver fails for ``self._kwargs`` assign when a type hint is added.

--------------------

Fixed
^^^^^
- "Component not supported" crash instead of no parameters (`141
<https://github.com/omni-us/jsonargparse/issues/141>`__).
- Default from ``default_config_files`` not shown in help when argument has no
default.
- Only ``init_args`` in later config overwrites instead of updates (`142
<https://github.com/omni-us/jsonargparse/issues/142>`__).

--------------------

Added
^^^^^
- Signature parameters resolved by inspecting the source code with ASTs
(`lightning11653
<https://github.com/Lightning-AI/lightning/issues/11653>`__).
- Support init args for unresolved parameters in subclasses (`114
<https://github.com/omni-us/jsonargparse/issues/114>`__).
- Allow providing a config with ``init_args`` but no ``class_path`` (`113
<https://github.com/omni-us/jsonargparse/issues/113>`__).

Fixed
^^^^^
- ``dump`` with ``skip_default=True`` not working for subclasses without
``init_args`` and when a default value requires serializing.
- ``JSONARGPARSE_DEFAULT_ENV`` should have precedence over given value.
- Giving an invalid class path and then init args would print a misleading error
message about the init arg instead of the class.
- In some cases ``print_config`` could output invalid values. Now a lenient
check is done while dumping.
- Resolved some issues related to the logger property and reconplogger.
- Single dash ``'-'`` incorrectly parsed as ``[None]``.

Changed
^^^^^^^
- ``dataclasses`` no longer an optional, now an install require on python 3.6.
- Parameters of type ``POSITIONAL_OR_KEYWORD`` now considered ``KEYWORD`` (`98
<https://github.com/omni-us/jsonargparse/issues/98>`__).
- Some refactoring mostly related but not limited to the new AST support.
- ``JSONARGPARSE_DEBUG`` now also sets the reconplogger level to ``DEBUG``.
- Renamed the test files to follow the more standard ``test_*.py`` pattern.
- Now ``bool(Namespace())`` evaluates to ``False``.
- When a ``class_path`` is overridden, now only the config values that the new
subclass doesn't accept are discarded.

Deprecated
^^^^^^^^^^
- ``logger`` property will no longer accept ``None`` in v5.0.0.

-------------------

Fixed
^^^^^
- ActionsContainer not calling ``LoggerProperty.__init__``.
- For type ``Union[type, List[type]`` when previous value is ``None`` then
``--arg+=elem`` should result in a list with single element.

Changed
^^^^^^^
- ``Literal`` options now shown in metavar like choices (`106
<https://github.com/omni-us/jsonargparse/issues/106>`__).
- ``tuple`` metavar now shown as ``[ITEM,...]``.
- Required arguments with ``None`` default now shown without brackets in usage.
- Improved description of ``--print_config`` in help.

-------------------

Added
^^^^^
- Support append to lists both from command line and config file (`85
<https://github.com/omni-us/jsonargparse/issues/85>`__).
- New ``register_unresolvable_import_paths`` function to allow getting the
import paths of objects that don't have a proper ``__module__`` attribute
(`lightning13092
<https://github.com/Lightning-AI/lightning/issues/13092>`__).
- New unit test for merge of config file ``init_args`` when ``class_path`` does
not change (`89 <https://github.com/omni-us/jsonargparse/issues/89>`__).

Changed
^^^^^^^
- Replaced custom pre-commit script with a .pre-commit-config.yaml file.
- All warnings are now caught in unit tests.
- Moved ``return_parser`` tests to deprecated tests module.

-------------------

Fixed
^^^^^
- ``sub_add_kwargs`` not propagated for parameters of final classes.
- New union syntax not working (`136
<https://github.com/omni-us/jsonargparse/issues/136>`__).