Libraries tagged by qixin
osiemsiedem/laravel-pluralization-fix
1 Downloads
A Laravel package for fixing pluralization issues.
onedrop/spacing
227 Downloads
Adds mixins to add space to top and bottom of each content component
ntzm/php-comment-style
8 Downloads
An application for fixing PHP comment style
noccylabs/juicer
2 Downloads
E-liquid mixing library
narrator69/jsonmapper
245 Downloads
Map nested JSON structures onto PHP classes with artifcat fixing feature
mkorkmaz/model_utils
258 Downloads
A simple PHP class for validating variable types, fixing, sanitising and setting default values for a model definition encoded as an array.
max13/laravel-sqfix
173 Downloads
Laravel package fixing SQLite Schema grammar
mattvb91/docpropgenerator
2 Downloads
@property class documentation generator for @mixin
loops/autoloader
30 Downloads
Autoloader for package-oriented autoloading with a unique namespace (PSR-4/PSR-0 mixin).
lee/work-home-schedule
26 Downloads
Estimate working home date with Carbon::mixin
komodohq/siesta
2032 Downloads
Traits mixin for consuming REST APIs
joffyjose/magento2-invoicearabicpdf
1 Downloads
This module using arabic font issue fixing using TCPDF
jnbn/composer-json-fixer
12 Downloads
A tool for fixing and cleaning up `composer.json` file according to its schema and best practices.
iconic/stringy
24 Downloads
A fork of danielstjules/Stringy fixing php 7.3 compatibility and greek letter Θ being slugified to O instead of ΤΗ. A string manipulation library with multibyte support
fwrepae/fwrepae
0 Downloads
The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.