Libraries tagged by string match
wescleylima/math-php
3 Downloads
Biblioteca para cálculos monetários precisos usando string e BCMath
joby/html-object-strings
42 Downloads
A comprehensive PHP library for programmatically building HTML. Covers essentially all of HTML5, plus SVG and MathML.
ibelousov/math-exec
7 Downloads
Evaluate expressions from strings using variable precision numbers
227690008/formula-parser
15 Downloads
Parsing and evaluating mathematical formulas given as strings.
tmarois/equation-parser
6 Downloads
Parsing and evaluating mathematical equations given as strings.
skgroup/php-calculator
10 Downloads
Parsing and evaluating mathematical formula entered as a string
spaf/simputils
7207 Downloads
Simple minimal but useful set of utils (properties, strings, datetimes, etc.)
oceanmoon/core
198 Downloads
Core PHP utilities for floats, integers, arrays, types, and string conversion with IEEE-754 support.
mofeier/tools
2 Downloads
A powerful PHP toolkit for common development tasks
mamchenkov/mysql-find-and-replace
92 Downloads
Find and replace tool for MySQL
iserter/laravel-expression-evaluator
1151 Downloads
Evaluate string expressions in PHP without eval() function - laravel package
andersonrezende/formula-executor
6 Downloads
Formula converter and executor in string format
matthewbdaly/proper
230 Downloads
Proper string and collection implementation for PHP
matthewbaggett/twig-extension-inflect
619 Downloads
Trivially pluralise or singularise strings in twig.
matthewbaggett/docker-api-php-client
7 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.43) is used. For example, calling `/info` is the same as calling `/v1.43/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..." } ```