Libraries tagged by reduce

Smarty Address Validation plugin for Shopware 6 integrates the Smarty Streets API to validate and standardize customer addresses at checkout, reducing failed deliveries.

Go to Download

Unifies and compresses js and css files in your AssetBundles. Uses internal server cache to speed up all the process, reducing the time wasting.

Go to Download

This Module allows negative deviations for product options eg. children reductions for events

Go to Download

Error-reducing base-27 encoding

Go to Download

Simple configuration layer around silex framework. With the aim of reducing spin up times with 'green field' projects.

Go to Download

Allows to control the quality of images using the UI. Optimizes images thereby reducing the overall storage size.

Go to Download

A high-performance binary storage system for PHP, reducing disk overhead and I/O operations

Go to Download

Standard Interface Library provides a set of interfaces for software developers to ensure compatibility of across various projects. Making them easily exchangeable and reducing to zero the overhead of making library compatible with projects using this standard.

Go to Download

Fast PHP file hashing library using intelligent sampling. Reads only selected portions of large binary files instead of full content, dramatically reducing I/O overhead. Automatically falls back to full-file hashing for text files. Deterministic, non-cryptographic, optimized for change detection.

Go to Download

Library for working with images (cropping and reducing, converting to base64, etc.)

Go to Download

Un programme de réduction en fonction de l'âge

Go to Download

PHP implementation of the Ramer-Douglas-Peucker algorithm for reducing the number of points on a polyline

Go to Download

Laravel Faker Generator for Dummies. This package intend to speed up development process by reducing time for new developer to learn faker package and help create a huge number of dummy data for testing purpose

Go to Download

AI-powered Laravel product catalog — generate listings from photo, keyword, URL, voice, datasheet, or bulk file, with multi-language, image intelligence, review workflow, JSON-LD, agentic shopping feeds (llms.txt), Digital Product Passport (DPP), social commerce video scripts, and returns reduction.

Go to Download

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.

Go to Download