Ynca

* Typing hint fixes
* Minor potential bugs found during type hint fixes

**Full Changelog**: https://github.com/mvdwetering/ynca/compare/v4.0.0...v4.0.1

What's Changed

As could be guessed from the major version increase, there are breaking changes in this release. Lots of things have moved or have been renamed to better match YNCA terminology and structure. Too many things to list have changed, but it should still be recognizable if you used this package before.

Next to making the API more consistent the new implementation also makes adding new functionality a lot easier.

Check the README.md and `example.py` for an overview of the current state.

These were the API guidelines followed during the 4.0.0 rewrite which may help when you are looking for things:

* YNCA functions have the same name on the Python API, but lowercase. Except when not possible due to Python naming restrictions like for 2CHDECODER which starts with a number.
* YNCA functions that can be read (and optionally written) are represented as attributes
* YNCA functions that can _only_ be written are represented as methods
* YNCA functions where writing results in an action are represented with methods (e.g. `vol_up()` which would otherwise be part of `vol` attribute).

As a bonus there are some newly added functions also:
* Party, PartyVol and PartyMute
* InitVolMode and InitVolLvl
* RemoteCode
* TwoChDecoder
* PureDirect mode

**Full Changelog**: https://github.com/mvdwetering/ynca/compare/v3.11.0...v4.0.0

What's Changed

Lots of things have moved or have been renamed to better match YNCA terminology and structure, but things should still be very recognizable if you used this package before.

Next to making the API more consistent the new implementation also makes adding new functions easier.

Check the README.md and `example.py` for an overview of the current state.

These were the guidelines followed during the 4.0.0 rewrite:

* YNCA functions have the same name on the Python API, but lowercase. Except when not possible due to Python naming restrictions like for 2CHDECODER which starts with a number.
* YNCA functions that can be read (and optionally written) are represented as attributes
* YNCA functions that can _only_ be written are represented as methods
* YNCA functions where writing results in an action are represented with methods (e.g. `vol_up()` which would otherwise be part of `vol`).

Added functions:
* Party, PartyVol and PartyMute
* InitVolMode and InitVolLvl
* RemoteCode
* TwoChDecoder
* PureDirect mode

**Full Changelog**: https://github.com/mvdwetering/ynca/compare/v3.11.0...v4.0.0b2

What's Changed

Lots of things have moved or have been renamed to better match YNCA terminology and API, but things should still be very recognizable if you used this package before.

Next to making the API more consistent the new implementation also makes adding new functions easier.

Check the README.md and example for an overview of the current state.

These were the guidelines followed during the API rewrite:

* YNCA functions that can be read (and optionally written) are represented as attributes
* YNCA functions that can _only_ be written are represented with methods
* YNCA functions where writing results in an action are represented with methods (e.g. `vol_up()` which would otherwise be part of `vol`).
* YNCA functions have the same name on the Python API, but lowercase. Except when not possible due to Python naming restrictions like for 2CHDECODER which starts with a number.

Added functions:
* Party, PartyVol and PartyMute
* InitVolMode and InitVolLvl
* RemoteCode
* TwoChDecoder
* PureDirect mode

**Full Changelog**: https://github.com/mvdwetering/ynca/compare/v3.11.0...v4.0.0b1

(release notes are a work in progress)

What's Changed

Lots of things have moved or have been renamed to better match YNCA terminology, but things should still be recognizable if you used this package before.

Next to making the API more consistent the new implementation also makes adding new functions easier.

Check the README.md and example for an overview of the current state.

These were the guildlines flollowed during the API rewrite:

* YNCA functions that can be read (and optionally written) are represented as attributes
* YNCA functions that can _only_ be written are represented with methods
* YNCA functions where writing results in an action are represented with methods (e.g. `vol_up()` which would otherwise be part of `vol`).
* YNCA functions have the same name on the Python API, but lowercase. Except when not possible due to Python naming restrictions like for 2CHDECODER which starts with a number.

Added functions:
* Party, PartyVol and PartyMute
* InitVolMode and InitVolLvl
* RemoteCode
* TwoChDecoder
* PureDirect mode

**Full Changelog**: https://github.com/mvdwetering/ynca/compare/v3.11.0...v4.0.0a2

(release notes are a work in progress)

Todo

* Move modelinfo
* Move server into package
* test terminal and server or exclude from coverage
* test connection??
* Update readme

What is new

(expand on lines below)
This is a breaking change
Easier to extend with more features
Mention API design guidelines with examples
* function name is attribute name in lowercase
* write only functions are methods
* actions are methods
* map function names directly, no magic
Mention quicks document

**Full Changelog**: https://github.com/mvdwetering/ynca/compare/v3.11.0...v4.0.0a1