exoapi_stripe v0.1.4

View Source ExOAPI.Stripe.Schemas.TestHelpers_testClock (exoapi_stripe v0.1.4)

description: A test clock enables deterministic control over objects in testmode. With a test clock, you can create objects at a frozen time in the past or future, and advance to a specific future time to observe webhooks and state changes. After the clock advances, you can either validate the current state of your scenario (and test your assumptions), change the current state of your scenario (and test more complex scenarios), or keep advancing forward in time.

:created :: :integer

Time at which the object was created. Measured in seconds since the Unix epoch.

:deletes_after :: :integer

Time at which this clock is scheduled to auto delete.

:frozen_time :: :integer

Time at which all objects belonging to this clock are frozen.

:id :: :string

Unique identifier for the object.

:livemode :: :boolean

Has the value true if the object exists in live mode or the value false if the object exists in test mode.

:name :: :string

The custom name supplied at creation.

:object :: :string

String representing the object's type. Objects of the same type share the same value.

:status :: :string

The status of the Test Clock.

Link to this section Summary

Types

params()
t()

Functions

changeset(struct \\ %__MODULE__{}, params)

Link to this section Types

Link to this type

params()

View Source 
@type params() :: map()
Link to this type

t()

View Source 
@type t() :: %ExOAPI.Stripe.Schemas.TestHelpers_testClock{
  created: integer() | nil,
  deletes_after: integer() | nil,
  frozen_time: integer() | nil,
  id: String.t() | nil,
  livemode: boolean() | nil,
  name: String.t() | nil,
  object: :"test_helpers.test_clock" | nil,
  status: (:ready | :internal_failure | :advancing) | nil
}

Link to this section Functions

Link to this function

changeset(struct \\ %__MODULE__{}, params)

View Source 
@spec changeset(t(), params()) :: Ecto.Changeset.t()