mpvipc-async

Author	SHA1	Message	Date
h7x4	ee5aa30335	core: mark `MpvDataType` as `serde(untagged)` Some checks are pending Build and test / build (push) Waiting to run Details Build and test / check (push) Waiting to run Details Build and test / test (push) Waiting to run Details Build and test / docs (push) Waiting to run Details	2024-12-15 16:21:25 +01:00
h7x4	3fe7417d4c	core: add docstrings for variants of `MpvCommand`	2024-12-14 13:52:57 +01:00
h7x4	eb7277e4fd	treewide: fix type for property change event ids	2024-12-14 13:51:12 +01:00
h7x4	ac863c571e	core_api: add `Default` for `Playlist`	2024-12-12 14:47:55 +01:00
h7x4	961da5b301	rename project from `mpvipc` to `mpvipc-async`	2024-08-03 17:07:09 +02:00
h7x4	93366593c7	Allow a few more highlevel types to be nullable	2024-08-03 15:38:46 +02:00
h7x4	650507e680	add support for parsing playlists as events + more This brings several changes with it: - `Mpv::get_property` now returns `Option`s in case `data` is nonexistent. There could be cases where this is different from `MpvDataType::Null` and `MpvDataType::MinusOne`. - `MpvError` now implements `PartialEq`	2024-05-04 18:45:32 +02:00
h7x4	e044246cba	fixup: fmt + clippy	2024-05-04 00:23:02 +02:00
h7x4	f1687fe07b	add/fix more docstrings	2024-05-04 00:23:01 +02:00
h7x4	878cebbc9f	use usize for request ids	2024-05-03 22:29:27 +02:00
h7x4	cb0921144d	rework error messages	2024-05-03 22:29:25 +02:00
h7x4	7eec34ce00	split property parsing from event parsing: All checks were successful Build and test / build (pull_request) Successful in 1m55s Details Build and test / check (pull_request) Successful in 1m52s Details Build and test / docs (pull_request) Successful in 2m21s Details Build and test / test (pull_request) Successful in 4m9s Details Build and test / check (push) Successful in 1m55s Details Build and test / build (push) Successful in 1m57s Details Build and test / docs (push) Successful in 2m43s Details Build and test / test (push) Successful in 5m33s Details High-level properties are now optional, considering there are about a thousand of them to parse. The high-level properties are a few chosen ones that I suspect might be useful for most people, with catch-all enum variants for the less common ones.	2024-05-02 21:16:23 +02:00
h7x4	f5ca2ebde9	add more tests, fix event/command response race condition All checks were successful Build and test / check (pull_request) Successful in 1m56s Details Build and test / build (pull_request) Successful in 1m57s Details Build and test / docs (pull_request) Successful in 2m30s Details Build and test / test (pull_request) Successful in 4m0s Details Build and test / check (push) Successful in 1m55s Details Build and test / build (push) Successful in 1m56s Details Build and test / docs (push) Successful in 3m2s Details Build and test / test (push) Successful in 3m59s Details	2024-05-01 23:45:42 +02:00
h7x4	64bf743c6c	clean: add docstrings, move a few things around	2024-05-01 22:22:45 +02:00
h7x4	7e20ff9b56	api: split into several files	2024-04-30 17:39:33 +02:00

15 Commits