ept_sdk

# Changelog

## 13.0.2

- [bug] Elixir already supports extended datetime parsing by default

## 13.0.1

- [bug] Support full ISO extended datetime parsing

## 13.0.0

- [breaking] Added a lot of new fields that we now support for purchases
- [breaking] Refactored completely how we define resource definitions

## 12.0.2

- [bug] `EPTSDK.sideload/2` didn't get the changes needed to allow for 422 exceptions

## 12.0.1

- [bug] Reducing constraints on `EPTSDK.sideload/2` to avoid having to constantly update

## 12.0.0

- [breaking] We weren't properly handling 5XX exceptions
- [breaking] The customer description was not settable or fetchable

## 11.0.1

- [bug] PaymentDemands.confirm with an EPTSDK record wasn't hitting the confirmation patch

## 11.0.0

- [breaking] Now enum fields are returned as atoms of the same value
- [breaking] `EPTSDK.fetch_money/2` deprecated in favor of a multimodal `EPTSDK.fetch_money/3` that takes a "type" like `:money` or `:atom`.
- [feature] PaymentDemand now has a `processor_state` property, from the API
- Added some documentation to the modules
- Updated libraries:
  - certifi 2.12.0 => 2.14.0
  - credo 1.7.11 => 1.7.12
  - earmark_parser 1.4.43 => 1.4.44
  - ex_doc 0.37.0 => 0.37.3
  - hackney 1.20.1 => 1.23.0
  - hpax 1.0.2 => 1.0.3
  - money 1.13.1 => 1.14.0
  - plug 1.16.1 => 1.17.0
  - plug_crypto 2.1.0 => 2.1.1
  - req 0.5.8 => 0.5.10

## 10.1.1

- [bug] When decoding responses the client wouldn't handle errors like it should, instead trying to encode it as a struct

## 10.1.0

- [feature] Allow for payment demands to be confirmed

## 10.0.2

- [bug] `EPTSDK.sideload/3` had an error pattern that was incorrectly defined as `EPTSDK.sideload/2` causing numerous issues

## 10.0.1

- [bug] Correcting some types, adding a new one, as well as the return value when no data comes back

## 10.0.0

- [breaking] sideload now can easily fit into the response from any `EPTSDK` api call instead of requiring a contorted series of steps
- [breaking] Now every api call returns `{:ok, resource_or_resources, included_list, client}` instead of the previous which didn't included the `included_list`.

## 9.0.0

- [breaking] Removing old relationships property now that we have codified results

## 8.0.1

- [bug] Two APIs still used includes, added tests to account for it.

## 8.0.0

- [breaking] [feature] Now relationships return the relation context (one to one or one to many)
- [breaking] No longer need the `included` list to be passed to structs
- [feature] New API `EPTSDK.sideload/3` which takes a list of records or record, an included list, and a list of things to load. This will replace the relationship structs with the actual relationships

## 7.0.0

- [breaking] Customers now have many addresses rather than one single address
- [breaking] We no longer automatically normalize relationships due to an infinite loop (fetch customers, include addresses, merchant, normalize customer -> addresses -> merchant -> addresses -> [...])
- [feature] You now have a reason for a relationship being unfetched

## 6.1.0

- [feature] You can now update a payment demand that isn't ready for processing

## 6.0.2

- [breaking] More changes to payment demand's interface

## 6.0.1

- [breaking] More changes to payment demand's interface
- [feature] Refund demands are now available

## 6.0.0

- [breaking] Payment demand has changed it's interface

## 5.0.2

- [fix] Removing an errant dbg() call.

## 5.0.1

- [fix] Update requests weren't sending the ID as part of the payload which is required by some JSONAPI servers.

## 5.0.0

- [breaking] With the new v2 endpoints we've officially moved away from the previous implementation. Not much has changed in terms of data, but a lot better naming:
  - charges to payment demand
  - refund demands split from charges
  - subscriptions to payment subscriptions
  - merchant accounts to merchants
  - users to accounts
- [breaking] We've also updated from a direct Finch integration to Req which has quickly become a community standard in Elixir. Instead of passing `finch_options`, you now pass an entire HTTP client. This also means we can drop the `json_encoder` and `json_decoder` options.
- [breaking] Allowing the usage of URIs for the `host` which is now called `location`

## 4.0.0

- [breaking] [business] We changed our domain name.

## 3.0.0

- [feature] Money properties now are parsed and we pulled more attributes over from charge
- [feature] Now when resource has a relationship we normalize it on the struct, for example `customer.address.merchant` will get you the merchant account of the consumer address of a customer.
- [breaking] [refactor] Rename `Address` to `ConsumerAddress`
- [breaking] [refactor] Renamed `property` property of PropertyNotFound to `name` as it reduces duplicitive naming.
- [breaking] [refactor] Removing `Dispute` because it isn't expressed in the HTTP API yet.
- [breaking] [refactor] The included values of a request are no longer stored on the `included` property of a `EPTSDK`

## 2.0.2

- [bugfix] Incorrectly parsing timestamps with the wrong ISO format.

## 2.0.1

- [bugfix] We weren't returning the type as part of the struct for resources
- [bugfix] Addresses didn't expose the `line_2` property

## 2.0.0

- [feature] [breaking] Now when the client recieves timestamps it will parse them with ISO Basic (8601).
- [feature] Fully fleshed out a ton more resources with their properties (to many to name)
- [feature] PropertyNotAvailable will now have a reason property that tells you why it is not available, as there are two reasons: unfetched and decoding error.

## 1.0.1

- [bugfix] When a request resulted in an error, like a timeout, it would fail in the middle of the library

## 1.0.0

- First release of the library