Libraries tagged by json models
marhone/transformer
24 Downloads
eloquent model to json resource
hitocean/laravel-generator
363 Downloads
it's a package to create actions and models form json
selami/entity
7 Downloads
A library to assert variable types and values for a model defined using JSON Schema standard (draft-07 and draft-06).
mogody/hyperf-resource
164 Downloads
Api resource classes allow you to expressively and easily transform your models and model collections into JSON
jspaceboots/laracrud
4 Downloads
Provides quick application scaffolding as well as HTML & JSON API interfaces for model CRUD.
emidia/yii2-jsonify
538 Downloads
Behavior that convert array to JSON before save data in model
brandonkerr/eloquent-from-settings
4 Downloads
Easily generate eloquent models and relationships from JSON or array
meiko/laravel-patchable
98 Downloads
Provides JSON API patch support to models
meiko/laravel-filterable
1286 Downloads
Provides JSON API filter support to models
marketo/silverstripe-script-genie
116 Downloads
A SilverStripe module which produces static JSON data files from specific models on-demand or onAfter{Write,Publish}
nooqta/larifriqiya
48 Downloads
A Laravel command that helps generate your models and migrations from a json file created with ifriqiya generator
drewlabs/mdl-cli
26 Downloads
PHP script for generating classes, interface, mixin, ect... based on UML model written in YAML or JSON language
yonna/core
20 Downloads
Yonna是一个极其纯净的纯API-PHP框架.轻松对接swoole、workerman,支持ajax/sw·http·websocket。人性及强力的DB-ORM,摆脱Model编程如连表自动前缀,类型自动转义/转换/解释有力的Response令api数据轻松转换,支持json/xml/html等格式化输出内置有趣的Exec方法,可实现服务、加密打包等方法轻松开启swoole,又或是将你的业务php代码混淆到难以阅读的效果
tslol/docker-api-php
2 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
piurafunk/docker-php
8 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```