Libraries tagged by repeat

A simple, repeatable field type

Go to Download

A simple, repeatable field type

Go to Download

Nest is a simple pseudo-programming language for defining repeatable and non-repeatable events in time.

Go to Download

Generic consumer and standard event message model meant to pull in a domain event message from rabbitmq and repeat it as a symfony event to all listening services

Go to Download

Scaffolding shopify apps with often repeated steps

Go to Download

This library provides the tools needed to create custom iterables without the need to repeat all the boilerplate code.

Go to Download

Report errors by mail while ignoring repeating ones.

Go to Download

Don't repeat yourself to place stats/ads script

Go to Download

Repeats requested variables back as a placeholder for javascript templates in laravel

Go to Download

Fulfills repeating concerns

Go to Download

Useful methods for not repeating myself

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 flexible PHP class for dynamic XML generation with support for attributes, repeating elements (@items), and pretty-printed output.

Go to Download

Report errors by mail while ignoring repeating ones.

Go to Download

HoneyComb CMS package checks if URLs is not repeating and if so creates a slug

Go to Download