Libraries tagged by calculation
icordeiro/kpi-calculator
8 Downloads
A lightweight PHP library for calculating KPIs like Average Ticket, Gross Margin, etc.
iamvimukthi/loancalculator
5 Downloads
A simple Laravel package for calculating loans, including EMI, interest, and total payments. Perfect for financial apps with easy integration and customizable options.
hunghbm/bagisto-fedex
7 Downloads
This extension used for calculating shipping rate with FeDex services.
hilinksnetworks/ng-paye-calculator
1 Downloads
A simple PHP library for calculating PAYE in Nigeria.
gleman17/laravel-geographical
53 Downloads
Easily add longitude and latitude columns to your records and use inherited functionality for calculating distances
giberti/array-functions
4 Downloads
Helpers for calculating descriptive statistics on arrays.
garethellis/cricket-stats-helper
37 Downloads
A simple PHP library for calculating cricket statistics such as batting average, bowling average and bowling economy. Can also convert number of overs bowled in scorecard notation to number of balls bowled, and vice-versa.
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.
futureweb/google-ip-prefix-diff-php
1 Downloads
PHP implementation of Google's Python script for calculating Google Cloud IP range differences.
dynamicscreen/laravel-geographical
252 Downloads
Easily add longitude and latitude columns to your records and use inherited functionality for calculating distances
durimjusaj/geo-bundle
13 Downloads
Doctrine functions for calculating geographical distances in your Symfony project.
dotplant/geo-calculator
50 Downloads
Calculating delivery cost based on fixed price and given customer address.
deviscoding/holidays
33 Downloads
PHP Library for calculating and managing holidays.
cysha/product-price-calculator
83 Downloads
A simple package to assist with calculating product prices
codesmithtech/amortize
67 Downloads
PHP library for calculating the amortization of mortgages, or any other loan, over a period of time