Libraries tagged by patch

Provides a simple and flexible way to patch Composer packages.

Go to Download

Simple Magento 2.4.7 patch for ACP2E-3130

Go to Download

Mirror of the pm-carousel javascript library tagged as a Drupal library (patched).

Go to Download

This a fork of the drupal/commerce_sermepa, ready for 10.x through the use of a patch.

Go to Download

Fork of PropelBundle with patches for PHP 7.x and Symfony 3.x compatibility.

Go to Download

The Drupal distribution for running Drupal with MongoDB as its backend. It has an automatically applied patch to update Drupal core.

Go to Download

This is a library to make CRUD's with your REST API. With this package, and some framework like Slim. You can abstract operations: POST,PUT,PATCH,DELETE,FIND,FINDONE at your Routes.

Go to Download

RedBeanPHP is an easy-to-use, on-the-fly ORM for PHP. Patched for 5.3.3.

Go to Download

payment patch version

Go to Download

A library for monkey patching relationships between Eloquent models at runtime

Go to Download

Connect to keycloak admin api easily - patch onto mohammad-waleed/keycloak-admin-client

Go to Download

Socialite patched to accept params from user in the urls

Go to Download

Standalone CodeIgniter3 DataBase Query Builder with monkey-patched technique.

Go to Download

Laravel Framework, patched with Anjara changes

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download