split property parsing from event parsing:
All checks were successful
Build and test / build (pull_request) Successful in 1m55s
Build and test / check (pull_request) Successful in 1m52s
Build and test / docs (pull_request) Successful in 2m21s
Build and test / test (pull_request) Successful in 4m9s
Build and test / check (push) Successful in 1m55s
Build and test / build (push) Successful in 1m57s
Build and test / docs (push) Successful in 2m43s
Build and test / test (push) Successful in 5m33s
All checks were successful
Build and test / build (pull_request) Successful in 1m55s
Build and test / check (pull_request) Successful in 1m52s
Build and test / docs (pull_request) Successful in 2m21s
Build and test / test (pull_request) Successful in 4m9s
Build and test / check (push) Successful in 1m55s
Build and test / build (push) Successful in 1m57s
Build and test / docs (push) Successful in 2m43s
Build and test / test (push) Successful in 5m33s
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.
This commit was merged in pull request #2.
This commit is contained in:
@@ -75,6 +75,7 @@ pub enum MpvDataType {
|
||||
Double(f64),
|
||||
HashMap(HashMap<String, MpvDataType>),
|
||||
Null,
|
||||
MinusOne,
|
||||
Playlist(Playlist),
|
||||
String(String),
|
||||
Usize(usize),
|
||||
|
||||
Reference in New Issue
Block a user