Libraries tagged by Charging
top20oferti/charts
101 Downloads
The laravel charting package
terdia/consoletvs-charts-clone
3 Downloads
The missing charting library on laravel, powered by Chartisan
syswatis/amountprecision
8 Downloads
Changing the display of custom product price to show 4 decimal places
sunnysideup/ecommerce_cloud_flare_geoip
125 Downloads
Provider additional country intelligence to e-commerce (where people are from, changing countries for testing, etc...)
sibilino/dygraphswidget
19 Downloads
Graphing and charting widget for Yii 1, based on Dygraphs.js
se7enxweb/ezownerchange
3 Downloads
eZ Publish Legacy extension which provides a simple solution for changing a content node creator field with the user selected. Great for smart developers!
rhyltonn/charts
14 Downloads
The laravel charting package
ptkrisnaanggara/chartjs
0 Downloads
The laravel charting package
prefeituradeavare/envswitch
25 Downloads
Switch between environments by changing .env file
phply/charts
26 Downloads
The missing charting library on laravel, powered by Chartisan
petesiss/phphc
741 Downloads
Wrapper for HighCharts js charting lib
peterfox/hieroglyph
14 Downloads
A package to simplify changing between different icon sets
pamitvn/consoletvs-charts
80 Downloads
The missing charting library on laravel, powered by Chartisan
nodeum-io/nodeum-sdk-php
0 Downloads
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>
nilsenpaul/slug-alert
185 Downloads
Warn your editors about the potentially negative side effects of changing slugs