Application, Context, Request, Response

rules/*.md

How to use

1. Identify the layer the task touches.
2. Open the matching

   rules/*.md

   below.
3. Prefer framework-native Bitrix patterns over custom abstractions.

Choose a rule file

When to read

rules/application-context.md

rules/application-context.md

Application and Context

• Application
• Context

When to read

rules/request.md

rules/request.md

HttpRequest and JSON body

• HttpRequest
• ParameterDictionary

When to read

rules/response.md

rules/response.md

HttpResponse and typed responses

• HttpResponse
• Built-in Response Classes
• Checklist
• Encrypted Cookies

When to read

rules/uri-uuid.md

rules/uri-uuid.md

Uri and UuidGenerator

• Uri
• UuidGenerator

Converter (not covered by rule files)

Bitrix\Main\Engine\Response\Converter

TO_SNAKE

TO_SNAKE_DIGIT

TO_CAMEL

TO_UPPER

TO_LOWER

LC_FIRST

UC_FIRST

KEYS

VALUES

RECURSIVE

process($data)

getFormat()

setFormat($format)

toJson()

Converter::OUTPUT_JSON_FORMAT

KEYS | RECURSIVE | TO_CAMEL | LC_FIRST

VALUES

use Bitrix\Main\Engine\Response\Converter;

(new Converter(Converter::LC_FIRST | Converter::TO_CAMEL))->process('la_la_land'); // laLaLand

(new Converter(Converter::OUTPUT_JSON_FORMAT))->process([
    'CATEGORIES' => [['ID' => 1, 'NAME' => 'Foods']],
]);
// ['categories' => [['id' => 1, 'name' => 'Foods']]] — 'Foods' stays untouched (no VALUES flag)

Checklist

• Opened only the rule file(s) needed for this task.
• Followed DI /

  /local/

  / security canons from

  AGENTS.md

  .