Total results: 201, showing 25 - 48

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

• type-infer 0.1.1

  
  A Clojure utility to inspect static types inferred by the Clojure compiler
  
• zookeeper-atom 1.0.0

  
  Provides a reference type that looks and behaves like a Clojure atom but uses Zookeeper to store and synchronize distributed access to it's value.
  
• com.roomkey/annotate 1.0.1

  
  Type annotations and type checking.
  
• slester/ring-browser-caching 0.1.1

  
  Provides ring middleware for browser cache hinting by file type
  
• org.clojars.darkleaf/di 3.6.0

  
  
• com.uswitch/kafka_2.9.2 0.8.0-SNAPSHOT

  
  kafka
  
• reloaded/lein-template 1.2.0

  
  A Leiningen 2 template to generate project skeletons using tools.namespace and a :dev profile with a dev.clj file.
  
• kongra/ch 0.1.30

  
  Low-cost dynamic type and constraints checks
  
• slava 0.0.31

  
  Infer specs from any Avro type
  
• java-time-dte 2018-04-18

  
  Datomic type extensions for java.time classes
  
• io.logicblocks/datatype.testing 0.0.1-RC11

  
  Utility functions for the testing other data type libraries.
  
• pghstore-clj 0.1.0

  
  Helper functions for working with PostgresSQL hstore data type in Clojure via JDBC
  
• cljsjs/decimal 10.2.0-0

  
  An arbitrary-precision Decimal type for JavaScript.
  
• io.logicblocks/datatype.bool 0.0.1-RC11

  
  Utility functions for the boolean data type.
  
• grafter/grafter.tabular-2 2.1.0

  
  Tools for the hard graft of data processing
  
• spootnik/mesomatic 1.0.1-r0

  
  Apache Mesos type conversions to and from Clojure
  
• axiom-clj/di 0.4.1

  
  Dependency Injection for Axiom
  
• org.clojars.michaelr524/cljs-uuid-utils 1.0.0-SNAPSHOT

  
  ClojureScript micro-library with an implementation of a type 4, random UUID generator compatible with RFC-4122 and cljs.core/UUID (make-random-uuid), a uuid-string conformance validating predicate (valid-uuid?), and a UUID factory from uuid-string with conformance validation (make-uuid-from).
  
• org.clojars.jasonjckn/kafka_2.9.2 0.7.2-test1

  
  
• labsoft-2018/common-labsoft 0.11.0-SNAPSHOT

  
  common code for labsoft 2 microservices
  
• edocu/clj-element-type 0.1.6-SNAPSHOT

  
  Clojure library with help fuctions for working with element type
  
• antler/caribou 0.4.5

  
  caribou: type structure interaction medium
  
• typeops 0.1.2

  
  Alternative type outcomes for arithmetic
  
• pager-duty-api 2.0

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