Libraries tagged by Work Code
rb-cohen/import-users-from-csv
24 Downloads
Fork to update and composer-ize import-users-from-csv plugin
comensee/php-google-translate
20 Downloads
Php Fork of the ruby google translate class
cmdev/mturk-php
49 Downloads
Provides a simple library to communicate with the Amazon Mechanical Turk API. This is a fork of ctrlcctrlv/mturk-php
greghubs/console-bundle
19 Downloads
This bundle allows you accessing the symfony4 console via your browser - fork from coreSphere bundle with SF4 compatibility added
fperezco/ratchetphp
1596 Downloads
A fork of PHP WebSocket library from cboden/ratchet
apaoww/yii2-websocket
34 Downloads
Yii2 websocket server component Fork From consik yii2 websocket used cboden/ractchet 0.4
raffaelj/cockpit-cms-editorformats
7 Downloads
Fork of pauloamgomes/cockpit-editorformats - Cockpit CMS v1 addon that extends core functionality by introducing the possibility to define editor format modes to the WYSIWYG field (based on tinymce editor).
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.
scribe/yuicompressor-library
307 Downloads
An up-to-date fork of Yahoo's JS and CSS compressor, kept in regular sync with upstream, except this one comes with a composer file.
scribe/closurecompiler-library
219 Downloads
An up-to-date fork of Google's Closure Compiler, kept in regular sync with upstream, except this one comes with a composer file.
phpfui/icalendar
9714 Downloads
A modern fork of the icalendar.org PHP implementation of rfc5545, management of iCal formatted files
lychee-org/nestedset
197329 Downloads
Nested Set Model for Laravel 10.0 and up (fork with patches for Lychee)
gammadia/slim-2.x
115026 Downloads
Fork of slim/slim with support for modern PHP versions.
ycodetech/valet-windows
1262 Downloads
A more enjoyable local development experience for Windows. A Windows port of the popular Laravel Valet and a fork of cretueusebiu/valet-windows, with new features.
coliving/commentable
28403 Downloads
Commentable Polymorphic Eloquent Models for for Laravel. This is fork from artisanry/commentable as it's abandoned