ResponseTemplateManager

Generate API response template string for given code and description

Get response template instance from template container

Create a CNR Response instance from a template id or raw response.

Instantiate the CNR response parser.

CNR compares templates on the CODE and DESCRIPTION hash keys.

Add response template to template container

Restore the brand's built-in templates, discarding everything {addTemplate()} has registered since.

The container is public static state with process lifetime, so a template registered for one scenario stays visible to every later one — across test classes in the same PHPUnit process, and in any long-lived consumer that registers templates per request. Call this when a scenario ends (e.g. from tearDownAfterClass()) so the next one starts from the brand defaults.

Scope, stated rather than implied: this is the counterpart of {\CNIC\addTemplate()}, not a general undo. It restores what the container held the first time addTemplate() ran for this class, so it is per brand and a no-op when the class was never added to. A direct assignment to the public $templates property is outside its reach — closing that second writer would mean making the property non-public, which {\CNIC\CNR\ResponseTranslator::templates()} reads across a class boundary, so it is a separate change. Go through addTemplate().

Return all available response templates

Check if given template exists in template container

Check if given API response hash matches a given template by code and description

Check if given API plain response matches a given template by code and description