Libraries tagged by alist

The Site Map URL Checker enables you to run an automatic checks for the response from a list of urls stored in a file.

Go to Download

Step in a list plugin for Textpattern

Go to Download

This repo contains a list of disposable and temporary email address domains often used to register dummy users in order to spam/abuse some services.

Go to Download

Provide a list of commands to create the laravel package, similar to artisan commands.

Go to Download

Symfony form-type that displays a list of the countries of the world grouped by continent

Go to Download

A list of all countries, optimized for Laravel 8

Go to Download

A git log parser that returns a list of commit objects

Go to Download

This extension generates a list of concerts for bands

Go to Download

Allows you to build a list of offers, each of which can be displayed in several categories

Go to Download

Simple twig variable for fetching a list of fetching countries

Go to Download

A library that returns a list of installed Composer packages.

Go to Download

A web scraper taking as arguments a list of URIs and a list of XPath queries to perform on each document. Returns an instance of DataInterface.

Go to Download

A tool for finding anagrams from a list of words (as an exercise of test-driven development).

Go to Download

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 - `>

Go to Download

A Behat output formatter which shows a list of scenarios' filename and line

Go to Download