1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
//! `Client` methods for the `BlacklistAPI` domain.
//!
//! # `add_to_blacklist`/`remove_from_blacklist`: removed
//!
//! The pre-8.0.4 port of this crate added `Client::add_to_blacklist`/
//! `Client::remove_from_blacklist` with an explicit "no `client.py` precedent" note. At v8.0.4,
//! `EeroClient` still has no such wrappers — device blocking moved to
//! [`Client::block_device`]/`Client::unblock_device`] (`crate::client::devices`), which invoke
//! the exact same underlying [`crate::endpoints::blacklist::BlacklistApi::add_to_blacklist`]/
//! [`crate::endpoints::blacklist::BlacklistApi::remove_from_blacklist`] domain methods and
//! already invalidate the `devices` cache bucket. Per
//! `.claude/tasks/briefs/v8/client.md` §5, these two `Client` methods are removed; the domain
//! methods themselves remain reachable via `client.api().blacklist()`, matching how
//! `EeroClient` exposes domain-API-only access for methods it never wraps.
use Client;
use crateEnvelope;
use crateError;