test: cover AI code review changes in CfClientTest (#2)
Build and Analyse / build-and-analyse (push) Successful in 30s

- live tests for API error details (status code, Cloudflare errors),
  404 on deleting an unknown record, unknown zones with and without
  emptyResultThrowsException, closing the client, multi-level
  subdomains and the zone apex, server- and client-side type filter,
  record attributes (priority, comment, SRV data) and Instant
  timestamps
- testPaging fetches all pages with a small page size, therefore
  CfDnsClient got a package-private constructor with a custom page size
- testDns checks that recordUpdate doesn't modify the given record
- SRV records: the priority is part of the data, fixed javadoc,
  README and changelog accordingly

refs #2

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
thischwaandClaude Opus 5.5 committed 2026-11-03 18:02:16 +01:00
1 parent 20fabf9667
commit c3a5c5f3e5
6 files changed
+229 -17

No files matched your search

+1 -1
View File
@@ -12,7 +12,7 @@
- batch DELETE sends only the record IDs, batch PATCH sends all writable attributes which aren't `null` (before: only the content)
- `CfDnsClient` uses one shared HTTP client with connection pooling instead of a new one per request and implements `AutoCloseable`, call `close()` to release the connections
- `CloudflareApiException` provides the HTTP status code (`getStatusCode()`) and the errors reported by Cloudflare (`getErrors()`)
- `RecordEntity` supports the attributes `priority` (MX, SRV, URI), `data` (e.g. SRV, CAA), `comment` and `tags`; they are also considered by batch operations, as is `proxied`
- `RecordEntity` supports the attributes `priority` (MX, URI), `data` (e.g. SRV incl. its priority, CAA), `comment` and `tags`; they are also considered by batch operations, as is `proxied`
- `recordCreate` and `recordUpdate` don't modify the given `RecordEntity` anymore and send only writable attributes
- fluent `update(content)` sends only the new content (partial update)
- filtering by exactly one record type is done by Cloudflare (`?type=`), unknown record types in responses don't break the client-side filter anymore