Skip to content

Declare the REST / SOAP clients and the cache adapter with their code - #86

Merged
njoubert-cleverage merged 1 commit into
mainfrom
bridges-client-codes
Oct 16, 2026
Merged

njoubert-cleverage merged 1 commit into
mainfrom
bridges-client-codes

Conversation

@njoubert-cleverage

Copy link
Copy Markdown
Member

Description

Follow-up of cleverage/rest-process-bundle#58, cleverage/soap-process-bundle#52 and cleverage/cache-process-bundle#53 (PR rest#59, soap#53, cache#54, merged): the clients and adapters tagged without code are registered with the deprecated addClient() / addAdapter().

config/services.yaml: code attribute on the 9 tags (4 REST clients, 4 SOAP clients, the memory cache adapter), the same code as the $code argument (getCode()).

Checked on the 27 demo.rest.*, demo.soap.*, demo.wiremock.* and demo.cache.* processes, with the bridges main: same exit codes as without the attribute, deprecations in the log 98 → 0; lint:container OK.

Breaking changes

None: the code attribute is ignored by the previous versions of the bridges.

🤖 Generated with Claude Code

…verage/cache-process-bundle#53 - Declare the clients and adapters with their code

Add the code attribute to the cleverage.rest.client, cleverage.soap.client
and cleverage.cache.adapter tags: the clients and adapters are loaded lazily
from the registries' service locators, without the addClient() /
addAdapter() deprecations (98 notices on the rest, soap, wiremock and cache
demos, 0 now).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@njoubert-cleverage
njoubert-cleverage merged commit 0980262 into main Oct 16, 2026
17 checks passed
@njoubert-cleverage
njoubert-cleverage deleted the bridges-client-codes branch October 16, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant