precision-soft/symfony-json-form
Composer 安装命令:
composer require precision-soft/symfony-json-form
包简介
forms that serialize to json for frontend frameworks with symfony api backends
README 文档
README
You may fork and modify it as you wish.
Any suggestions are welcomed.
Purpose
The purpose of this library is to create forms for single page applications, with a symfony backend. The forms are constructed in the backend and serialized to json, that can be rendered in the frontend. In the assets folder you can find a react component to render the form.
A form is described by three pieces that you provide per form:
- a DTO (
DtoInterface) — the typed data structure the form maps to and from; - a form service (
AbstractFormService) — declares the HTTP method, the submit action, and the elements; - the elements — the individual fields (
NumberElement,StringElement, ...).
render() serializes the form (plus the DTO values) to a json structure for the frontend; handleRequest() takes the
incoming request, sanitizes it, and denormalizes it back into the DTO.
V1 vs V2
There are 2 versions of the react renderer. They consume the same backend json — only the frontend components differ:
- formV1 — the original react components, kept for backwards compatibility.
- formV2 — the new components and the recommended way to render the json.
Usage
Add this to your services.yaml so every form service receives the serializer:
services: _instanceof: PrecisionSoft\Symfony\JsonForm\Service\Contract\AbstractFormService: calls: - [ setSerializer, [ '@serializer' ] ]
A form service must implement four abstract methods: getDtoClass(), getMethod(), getAction(DtoInterface $dto)
and build(Form $form, DtoInterface $dto).
<?php declare(strict_types=1); namespace Acme\Form; use Acme\Dto\ProductEditDto; use PrecisionSoft\Symfony\JsonForm\Contract\DtoInterface; use PrecisionSoft\Symfony\JsonForm\Element\ArrayElement; use PrecisionSoft\Symfony\JsonForm\Element\NumberElement; use PrecisionSoft\Symfony\JsonForm\Form\Action; use PrecisionSoft\Symfony\JsonForm\Form\Form; use PrecisionSoft\Symfony\JsonForm\Service\Contract\AbstractFormService; use Symfony\Component\HttpFoundation\Request; class ProductEditForm extends AbstractFormService { protected function getDtoClass(): string { return ProductEditDto::class; } protected function getMethod(): string { return Request::METHOD_POST; } protected function getAction(DtoInterface $dto): Action { return new Action('product-edit', ['id' => $dto instanceof ProductEditDto ? $dto->getId() : null]); } protected function build(Form $form, DtoInterface $dto): void { $form->addElement(new NumberElement('id', 'Id')) ->addElement(new ArrayElement('status', 'Status', ['active' => 'Active', 'inactive' => 'Inactive'])); } }
<?php declare(strict_types=1); namespace Acme\Dto; use PrecisionSoft\Symfony\JsonForm\Contract\DtoInterface; class ProductEditDto implements DtoInterface { private int $id; private string $status; public function getId(): int { return $this->id; } public function setId(int $id): self { $this->id = $id; return $this; } public function getStatus(): string { return $this->status; } public function setStatus(string $status): self { $this->status = $status; return $this; } }
<?php declare(strict_types=1); namespace Acme\Controller; use Acme\Dto\ProductEditDto; use Acme\Form\ProductEditForm; use Acme\Service\ProductEditService; use Symfony\Bundle\FrameworkBundle\Controller\AbstractController; use Symfony\Component\HttpFoundation\Request; use Symfony\Component\HttpFoundation\Response; class ProductController extends AbstractController { public function edit(Request $request, ProductEditForm $productEditForm, ProductEditService $productEditService): Response { $id = (int)$request->get('id'); if (Request::METHOD_POST === $request->getMethod()) { /** @var ProductEditDto $dto */ $dto = $productEditForm->handleRequest($request); $productEditService->save($dto); } else { $dto = $productEditService->createDto($id); } return $this->json(['form' => $productEditForm->render($dto)]); } }
Form elements
Each element renders to a json node with a type the frontend dispatches on. All take name and label first;
the most relevant extra constructor arguments are noted below.
| Element | json type |
Extra arguments |
|---|---|---|
StringElement |
string |
— |
NumberElement |
number |
?float $min, ?float $max, ?float $step |
BoolElement |
bool |
— |
DateElement |
date |
string $format = 'Y-m-d', ?string $min, ?string $max |
DateTimeElement |
dateTime |
string $format = 'Y-m-d H:i', ?string $min, ?string $max |
PasswordElement |
password |
— |
HiddenElement |
hidden |
(label is not required) |
LabelElement |
label |
display-only |
FileElement |
file |
— |
ArrayElement |
array |
array $options, string $mode (MODE_SINGLE/MODE_MULTIPLE) |
AutocompleteElement |
autocomplete |
string $route, string $mode, string $parameter = 'query' |
CollectionElement |
collection |
nested elements via addElement() |
PrototypeCollectionElement |
prototypeCollection |
nested elements via addElement() (repeatable) |
ArrayElement and AutocompleteElement throw InvalidModeException for an unknown $mode. Element names must be
alphanumeric (ctype_alnum) — this is enforced and intentional.
DateElement and DateTimeElement validate the value strictly against $format: a value that does not round-trip
through the format (e.g. an overflow date such as 2021-02-30) throws InvalidValueException. When $min and/or
$max are set, the value is also enforced server-side to fall within that inclusive range — an out-of-range value
throws InvalidValueException. CollectionElement
and PrototypeCollectionElement throw InvalidValueException when the value — or, for the prototype collection, any
item — is not an array.
Request handling and sanitization
handleRequest(Request $request, ?DtoInterface $dto = null, bool $sanitizeData = true):
- For
GETthe data is read from the query string; forPOST/PUT/PATCHfrom the json body (falling back torequest->all()when the body is empty). - A request body that decodes to a non-array scalar (e.g.
5) throws anExceptionrather than a rawTypeError. - Pass an existing
$dtoto populate it in place (OBJECT_TO_POPULATE) — useful forPATCH/PUT.
When $sanitizeData is true (default), sanitizeData() applies the following rules before denormalization:
- empty arrays are dropped — an absent nested structure does not override DTO defaults;
- empty strings are kept — so a
PATCH/PUTcan explicitly clear a field by sending"".
Pass sanitizeData: false to denormalize the raw payload unchanged.
React
Use the components from ./assets/react to interpret the backend response. This package ships the sources only; the host application is responsible for bundling them (there is no build step here). The Config component is project specific — it holds the locale context of the application. It is integrated with:
willdurand/js-translation-bundlefor the Translator.friendsofsymfony/jsrouting-bundlefor the UrlGenerator.
Tests
PHP tests run in the dev container:
./dc exec dev php vendor/bin/simple-phpunit
The framework-agnostic react asset services (e.g. service/Utility.ts) are covered by a dependency-free harness using
Node's built-in test runner (the dev container ships Node):
./dc exec dev sh -c 'cd assets/react && npm test'
Dev
git clone git@gitlab.com:precision-soft-open-source/symfony/json-form.git cd json-form ./dc build && ./dc up -d
Todo
- Render and handle complex types like
\DateTimein DTO denormalization.
precision-soft/symfony-json-form 适用场景与选型建议
precision-soft/symfony-json-form 是一款 基于 TypeScript 开发的 Composer 扩展包,目前已累计 20 次下载、GitHub Stars 达 0, 最近一次更新时间为 2024 年 09 月 18 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「symfony」 「json」 「form」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 precision-soft/symfony-json-form 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 precision-soft/symfony-json-form 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 precision-soft/symfony-json-form 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Kinikit - PHP Application development framework MVC component
The bundle for easy using json-rpc api on your project
Diese Contao 4 Erweiterung stellt Google reCAPTCHA V2 in Form eines neuen Formularfeldes im Formulargenerator bereit. This extension provides Google reCAPTCHA V2 in the form of a new form field in the form generator of Contao Open Source CMS.
ext-json wrapper with sane defaults
A package to cast json fields, each sub-keys is castable
A Laravel Filament Forms slug field.
统计信息
- 总下载量: 20
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 16
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2024-09-18