Clojars

Clojars

Search for 'the'

For details on the search query syntax, see the guide.

Total results: 2946, showing 601 - 624

Note: artifacts in italics are non-canonical forks. See the wiki for more details.


  • The Québécois swear generator

  • Clojure core documentation as provided by the Clojure Grimoire. This JAR contains the data from https://github.com/clojure-grimoire/datastore and https://github.com/clojure-grimoire/doc-clojure-core, converted to the Grenada format (https://github.com/clj-grenada). For licensing terms, see http://conj.io/about.

  • Compare clojure data structures. The differences come back as a list with paths to where the elements differ

  • Common CLI functions for the DE backend services and tools
  • webnf/async-servlet 0.2.0-SNAPSHOT

    A servlet 3.0 implementation, that enables the async api for ring applications

  • Utility functions for the testing other data type libraries.

  • Transform and optimize images for serving over the web - either as a Ring middelware, or to disk.

  • Structural scraping for the rest of us.
  • avenir 0.2.2

    Clojure utilities which may find a proper home in the future

  • Utility for using the PSB2 program synthesis datasets.

  • Clojure implementation of the xoroshiro128+ PRNG described at http://xoroshiro.di.unimi.it/

  • A client to talk to the Google Cloud API (based on clj-http).
  • clj-btc 0.11.2

    Clojure bindings for the original (C++) Bitcoin Client

  • The MIT Java Wordnet Interface

  • Standalone build of Babel for use in non-Node.js environments, including browsers. Similar to the (now deprecated) babel-browser.

  • When running the repl, reload every time a file is saved.

  • Implementation of the sv/blob-storage protocol for Google Cloud Storage.

  • The PagerDuty API provides programmatic access to entities within a PagerDuty account. It is designed around [RESTful principles](https://en.wikipedia.org/wiki/Representational_state_transfer) with a path structure based on resources and their relationships. All requests and responses are serialized in [JSON](https://en.wikipedia.org/wiki/JSON), including error responses. Schema are designed to be reusable across requests and across endpoints. More sophisticated API clients should treat PagerDuty resources as unique objects keyed by the `id` field that can be used in any API request involving resources of that type. Every resource contains a `type` field that identifies the schema it uses. ## Rate limiting Each account and authentication mechanism is limited to the number of API requests it can make every minute. API requests that exceed the API rate limit will return an [HTTP status code](error_codes.html#http_responses) of 429. Different requests may affect your rate limit differently, so clients should always be prepared to be rate limited and respond appropriately. ## Read-Only API Keys API requests made with read-only keys attempting to access endpoints with methods other than `GET` will return an [HTTP status code](error_codes.html#http_responses) of 403. ## Error Codes Most APIs will return an error code from an unsuccessful call. They are described [here](error_codes.html).

  • A timbre appender for the Google Cloud Logging service

  • Provides the core functions and protocols necessary for a bitsplit implementation

  • Utility functions for the boolean data type.

  • The Burning Swell web application

  • Ring middleware to add an Accept header to every web request based off of the URL extension.

  • Pure Clojure library for interacting with the Twilio REST API, to send SMS messages
← Previous23242526272829Next →