Search for 'the'

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

Total results: 3049, showing 625 - 648

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


  • The build protocols for the Phoenix runtime, so that Components don't have to depend on Phoenix core.

  • Structural scraping for the rest of us.
  • st/common 0.10.10

    The Standard Treasury Common Library

  • A library to bridge the gap between CLJ/CLJS, web-sockets and core.async

  • Used in the migratus tests.

  • Clojure bindings and exploration of the tvm library

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

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

  • 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).

  • The irresistible Clojure IDE-in-a-plugin

  • The backend for ALai57's blogging app

  • shipping the data from JDBC storage via REST-API with API spec

  • The JTS Topology Suite is an API for modelling and manipulating 2-dimensional linear geometry. It provides numerous geometric predicates and functions. JTS conforms to the Simple Features Specification for SQL published by the Open GIS Consortium.
    This artifact may shadow a release on Maven Central. You should search there for a canonical release.

  • Utility functions for the testing other data type libraries.

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

  • Additional utilities for the Reitit router.

  • Aviary module for manipulating the filesystem.
  • avenir 0.2.2

    Clojure utilities which may find a proper home in the future

  • Muotti is a graph based value transformer library which aims to solve value transformation by utilizing a digraph of known transformations to produce a transformer chain which is then used to perform the actual transformation.

  • CommonMark is a rationalized version of Markdown syntax. It provides a library with functions for parsing CommonMark documents to an abstract syntax tree (AST), manipulating the AST, and rendering the document to HTML or to an XML representation of the AST.

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

  • A Clojure Library for the Facebook Messenger Platform

  • Selectize is the hybrid of a textbox and <select> box.

  • The Burning Swell scheduler