Libraries tagged by json_matchers

PHP Matcher enables you to match values with patterns

Go to Download

Simplifies and standardizes seeding from JSON files named to match the table they will be populating

Go to Download

Simplifies and standardizes seeding from JSON files named to match the table they will be populating

Go to Download

Json file based redirects with exact match and wildcard * matching for changing higher up paths with sub categories so the sub categories get redirected as well.

Go to Download

Ultra-fresh PHP matching functions

Go to Download

Run dynamic JSON based CLI's with mix and match support for task runtimes.

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

A configuration loader, where order matters.

Go to Download

small php micro framework: json service

Go to Download

Converts Magento's Quality Patches to a JSON format to be used with vaimo/composer-patches

Go to Download

Simple library for applying JSON Patches (RFC 6902) to PHP data structures

Go to Download

Twig and JSON static site generator. Includes watcher for view file changes in frontend development and an API for other pure frontend projects.

Go to Download

This tool utilizes Rector json output to create composer patches for third-party packages.

Go to Download

Execute RFC 6902 compliant patches in PHP

Go to Download

Mother's friend's son's validator

Go to Download