rithlock/vich-uploader-serialization-bundle
Composer 安装命令:
composer require rithlock/vich-uploader-serialization-bundle
包简介
Provides integration between VichUploaderBundle and JMSSerializerBundle.
关键字:
README 文档
README
Provides integration between VichUploaderBundle and
JMSSerializerBundle.
Allows to generate full or relative URIs to entity fields mapped with @Vich and @JMS annotations during the serialization.
Requirements
- PHP 7.1 and later
- Symfony 3.4, 4.3 and later
Installation
composer req fresh/vich-uploader-serialization-bundle='~2.4'
Usage
Add the next class to the use section of your entity class.
use Fresh\VichUploaderSerializationBundle\Annotation as Fresh;
Bundle provides two annotations which allow the serialization of @Vich\UploadableField fields in your entities.
At first you have to add @Fresh\VichSerializableClass to the entity class which has uploadable fields.
Then you have to add @Fresh\VichSerializableField annotation to the uploadable field you want to serialize.
Annotation @Fresh\VichSerializableClass does not have any option.
Annotation @Fresh\VichSerializableField has one required option value (or field) which value should link to the field with @Vich\UploadableField annotation.
It can be set like this @Fresh\VichSerializableField("photoFile") or @Fresh\VichSerializableField(field="photoFile").
Also there is another option includeHost, it is not required and by default is set to true.
But if you need, you can exclude the host from the generated URI, just use the next variant of the annotation @Fresh\VichSerializableField("photoFile", includeHost=false).
And also don't forget that to serialize Vich uploadable fields they also should be marked with @JMS annotations to be serialized.
The generated URI by default:
{
"photo": "http://example.com/uploads/users/photos/5659828fa80a7.jpg",
"cover": "http://example.com/uploads/users/covers/456428fa8g4a8.jpg",
}
The generated URI with includeHost set to false:
{
"photo": "/uploads/users/photos/5659828fa80a7.jpg",
"cover": "/uploads/users/covers/456428fa8g4a8.jpg",
}
Example of entity with serialized uploadable fields
<?php namespace AppBundle\Entity; use Doctrine\ORM\Mapping as ORM; use Fresh\VichUploaderSerializationBundle\Annotation as Fresh; use JMS\Serializer\Annotation as JMS; use Vich\UploaderBundle\Mapping\Annotation as Vich; /** * @ORM\Table(name="users") * @ORM\Entity() * * @Vich\Uploadable * * @Fresh\VichSerializableClass */ class User { /** * @var string * * @ORM\Column(type="string", length=255) * * @JMS\Expose * @JMS\SerializedName("photo") * * @Fresh\VichSerializableField("photoFile") */ private $photoName; /** * @var File * * @JMS\Exclude * * @Vich\UploadableField(mapping="user_photo_mapping", fileNameProperty="photoName") */ private $photoFile; /** * @var string * * @ORM\Column(type="string", length=255) * * @JMS\Expose * @JMS\SerializedName("cover") * * @Fresh\VichSerializableField("coverFile", includeHost=false) */ private $coverName; /** * @var File * * @JMS\Exclude * * @Vich\UploadableField(mapping="user_cover_mapping", fileNameProperty="coverName") */ private $coverFile; }
Don't make a mistake!
Additional example of a wrong usage of provided annotations to attract your attention.
Use @Fresh\VichSerializableField only with the field which is mapped with @ORM\Column,
because this field is mapped to a database and keeps the name of the stored file.
Don't use the @Fresh\VichSerializableField with a field which also mapped with @Vich\UploadableField,
this is a wrong use case and will throw an exception!
So the next example is the incorrect usage of provided annotations! Don't do so!
<?php namespace AppBundle\Entity; use Doctrine\ORM\Mapping as ORM; use Fresh\VichUploaderSerializationBundle\Annotation as Fresh; use JMS\Serializer\Annotation as JMS; use Vich\UploaderBundle\Mapping\Annotation as Vich; /** * @ORM\Table(name="users") * @ORM\Entity() * * @Vich\Uploadable * * @Fresh\VichSerializableClass */ class User { /** * @var string * * @ORM\Column(type="string", length=255) */ private $photoName; /** * @var File * * !!! Next three annotations should be moved to the `photoName` property * @JMS\Expose * @JMS\SerializedName("photo") * @Fresh\VichSerializableField("photoFile") * * !!! This annotation should be left here * @Vich\UploadableField(mapping="user_photo_mapping", fileNameProperty="photoName") */ private $photoFile; }
Contributing
See CONTRIBUTING file.
rithlock/vich-uploader-serialization-bundle 适用场景与选型建议
rithlock/vich-uploader-serialization-bundle 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 2.98k 次下载、GitHub Stars 达 0, 最近一次更新时间为 2021 年 12 月 01 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「symfony」 「serialization」 「bundle」 「upload」 「JMSSerializerBundle」 「integration」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 rithlock/vich-uploader-serialization-bundle 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 rithlock/vich-uploader-serialization-bundle 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 rithlock/vich-uploader-serialization-bundle 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Fork of jms/serializer 1.14.1 with support for modern PHP versions.
2lenet/EasyAdminPlusBundle
De/normalize business objects without tightly coupling them to your normalization format
The bundle for easy using json-rpc api on your project
Provide a way to secure accesses to all routes of an symfony application.
DMS Meetup API Bundle, enables Meetup API clients in services
统计信息
- 总下载量: 2.98k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 14
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2021-12-01