Liking cljdoc? Tell your friends :D

ventas.database.generators

User-friendly generators

User-friendly generators
raw docstring

ventas.email.templates.core

No vars found in this namespace.

ventas.email.templates.password-forgotten

No vars found in this namespace.

ventas.email.templates.user-registered

No vars found in this namespace.

ventas.entities.address

No vars found in this namespace.

ventas.entities.brand

No vars found in this namespace.

ventas.entities.configuration

Don't use this namespace, as it's on the way out. Create an entity type if you want to store config in the db.

Don't use this namespace, as it's on the way out.
Create an entity type if you want to store config in the db.
raw docstring

ventas.entities.core

No vars found in this namespace.

ventas.entities.country

No vars found in this namespace.

ventas.entities.currency

No vars found in this namespace.

ventas.entities.event

No vars found in this namespace.

ventas.entities.menu

No vars found in this namespace.

ventas.entities.product-review

No vars found in this namespace.

ventas.entities.product-taxonomy

No vars found in this namespace.

ventas.entities.product-term

No vars found in this namespace.

ventas.entities.site

No vars found in this namespace.

ventas.entities.state

No vars found in this namespace.

ventas.i18n

Server-side tongue wrapper

Server-side tongue wrapper
raw docstring

ventas.i18n.cldr

CLDR importer. Supports countries and states. See http://cldr.unicode.org for more information.

CLDR importer. Supports countries and states.
See http://cldr.unicode.org for more information.
raw docstring

ventas.payment-method

The API for registering payment methods. Payment methods are responsible for:

  • Transforming an :order entity into the shape they need
  • Making the HTTP requests they need and handling them correctly
  • Updating the :order with the resulting :payment-reference and :payment-amount
  • Changing the status of the :order from :draft to :paid or :unpaid If an error occurs, it should be registered in the event log, and the order should be left unmodified.

To allow the payment methods to do their work, they can do anything they need, but most likely they'll want to:

  • Register Ring handlers: use ventas.plugin's :http-handler
  • Make HTTP requests: clj-http is included as a dependency
The API for registering payment methods.
Payment methods are responsible for:
  - Transforming an :order entity into the shape they need
  - Making the HTTP requests they need and handling them correctly
  - Updating the :order with the resulting :payment-reference and :payment-amount
  - Changing the status of the :order from :draft to :paid or :unpaid
If an error occurs, it should be registered in the event log, and the order should be
left unmodified.

To allow the payment methods to do their work, they can do anything they need, but most likely
they'll want to:
  - Register Ring handlers: use ventas.plugin's :http-handler
  - Make HTTP requests: `clj-http` is included as a dependency
raw docstring

ventas.search.entities

Generic fulltext entity search

Generic fulltext entity search
raw docstring

ventas.server.http-ws

Exposes the WS api through an HTTP endpoint.

Exposes the WS api through an HTTP endpoint.
raw docstring

ventas.system

Utilities for managing the state of the system

Utilities for managing the state of the system
raw docstring

ventas.utils.jar

See https://stackoverflow.com/questions/22363010/get-list-of-embedded-resources-in-uberjar
raw docstring

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close