Libraries tagged by time to read

The Inspeya Google Reviews module is designed to integrate Google Reviews into your Magento 2 store. This module allows you to display customer reviews from Google directly on your product pages, enhancing credibility and trustworthiness. With full backend manageability, you can easily configure and display reviews, providing a seamless integration that enhances the customer shopping experience. Key features include real-time review updates, customizable display options. Required dependencies include mhinspeya/backend-mod for support configuration.

Go to Download

Go the extra mile to perfect the last mile delivery with Logistia. Optimize routes with real-life factors like the number of orders and drivers, vehicle load, lunch breaks, or and tight time windows while you drink your coffee.

Go to Download

The Drupal AI Chatbot module leverages OpenAI's language models to add an intelligent chatbot to your Drupal site. It analyzes user interactions and provides real-time assistance, information retrieval, and interactive experiences for website visitors.

Go to Download

Module to display product on the home page and update stock in real time

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

Middleware to save the response time into the X-Response-Time header

Go to Download

PHP middleware to add a Response Time header

Go to Download

A GuzzleHTTP Middleware that adds a X-Request-Duration header to all responses to monitor response times.

Go to Download

A simple helper class for Server Timing. Easily profile your code's execution time and send it to the client via the Server-Timing header.

Go to Download

Set cache headers correctly as a Middleware in laravel, you can pass a unix time to last_modified

Go to Download

Class to calculate delivery lead times expressed in working days. Can be adapted easily for various countries using sub-classes, just submit PRs

Go to Download

WeCommerce is an eCommerce ecosystem designed for everyone to build and scale their business. It offers a wide range of functionalities that allows you to have full control of your store. It is combined with easy product information management and fast response time.

Go to Download

This repository contains Aspose Cloud SDK for PHP source code. Aspose Cloud SDK for PHP lets PHP developers convert and process a variety of file formats in the cloud quickly and easily.

Go to Download

This PSR-15 middleware adds an X-Response-Time in milliseconds to the Response header.

Go to Download

Archive database tables which have grown over time to different tables,time-suffixed, to free commonly-used tables of this dead weight.

Go to Download