ruby-whatsapp 0.4.0 → 0.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8b4ff5c9b9ee2bea36b889af8a3d153bb2e166d233ad9bfc51e20f9ec19ab9e7
-  data.tar.gz: 8d419f24aae3b21d0218bb95c68c4f75dec56ebdafb4c0447d7ec29e8def7b7b
+  metadata.gz: 7fa9a4e0fe14f7868639ddb3fe8285801aba43d4c92ae5decf7f8d7e5e80882e
+  data.tar.gz: 534f91cc1841a1be0b9740619360287dcc0ee9cfc6d82b3ba12fde421cdbc81e
 SHA512:
-  metadata.gz: 9c7d6fbfe3783788238af4ec52c683a122099f85fd7c408d94e09bc9a672b5594167e2de6bc05dfb85148f517bfee8c159d7f3f579191ae66020d05f3797cac5
-  data.tar.gz: 0d55554385a2fb98318996292131a59c64bed7206766d3b20d7c3033077232e02d5a24878db7e31b12e66b35270698ad892f1e0759468ae656baeda39e271f92
+  metadata.gz: dd34f6bd15f531af85b31feeeb767290abcb82c291b03cbd02398ce310cb752140c31ba9e1b37b5e36db796c4992126be2dadc12b1041a2ab67f114c71a20a6c
+  data.tar.gz: 1a5afbd7d50790859e60340e87856574f7b53f6c647191c5b7d639023efd1e6129e2f37010c6f513dbc429aaa4b09d3ac87903dca86dff0e8d6f0cce4dcf20bd

data/CHANGELOG.md

@@ -1,3 +1,12 @@
+## [0.4.2] - 2026-08-19
+
+- Add WhatsApp Business Profile management: `Whatsapp::BusinessPhoneNumber::Profile::Get` reads the public card a WhatsApp user sees before they reply — about text, description, address, email, websites, industry vertical, and profile picture URL — and `::Profile::Update` writes them. Unlike `::Account`, this is not an exception to the module's `phone_id` rule: Meta exposes the profile as an edge on the phone number itself (`GET`/`POST /{phone_id}/whatsapp_business_profile`), so both actions reuse the existing `BusinessPhoneNumber::Transport#edge_path` unchanged — no new transport, no new ID to configure. `Update` validates the 21-value `Profile::Verticals` enum and Meta's documented limits (about 139, address 256, description 512, email 128 characters, at most 2 websites) before any request is made, and compacts omitted fields out of the body rather than sending null — which Meta reads as an instruction to blank them — with an empty `websites` array surviving on purpose, since that is how the list is cleared. `email`'s format is deliberately left to Meta, which validates it server-side; a regex here would reject valid exotic addresses. It reuses the existing `BusinessPhoneNumber::Response`, since the endpoint answers a bare `{success}`.
+- `Profile::Details` owns Meta's `data` envelope so callers never reach through it. Meta's reference declares the entry as `{"business_profile": {...}}` while live responses are observed to carry the profile fields directly in `data[0]`; `deserialize` reads both rather than betting on one, following the same flatten-the-meaningless-wrapper habit as `SubscribedApp::Response::App` and `MessageTemplates::Response::Paging`. Its `vertical` stays a raw string, never validated or upcased on the way in, so a value Meta adds later still round-trips — compare it against `Verticals::ALL`.
+
+## [0.4.1] - 2026-08-18
+
+- Add WhatsApp Business Account details and updates: `Whatsapp::BusinessPhoneNumber::Account::Get` reads the WABA node — name, timezone, message template namespace, country, and the review, verification, and ownership state — and `::Account::Update` renames the account or moves its timezone. `Get` returns an `Account::Details` carrying `ReviewStatuses`/`VerificationStatuses`/`OwnershipTypes` constants and `#approved?`/`#verified?`/`#self_owned?` predicates; statuses stay raw strings and are never validated on the way in, so a value Meta adds later still round-trips. `Update` validates locally that at least one of `name`/`timezone_id` is present and non-blank before any request is made, and reuses the existing `BusinessPhoneNumber::Response` since the endpoint answers a bare `{success}`. These two live under `BusinessPhoneNumber` but address `waba_id` rather than `phone_id` — the module's one account-scoped corner — so they carry their own transport.
+
 ## [0.4.0] - 2026-08-14
 
 - Add subscribed apps management: `Whatsapp::SubscribedApp::List`, `::Subscribe`, and `::Unsubscribe` wrap the `subscribed_apps` edge — the switch that turns a WABA's webhook delivery on or off, as opposed to `Whatsapp::Webhook`, which only deserializes notifications once Meta is already sending them. Responses expose `Collection`, `Subscription`, and `Unsubscription`, each composed from a shared `App` value object.