Version - 0.2.6

What's Changed

• UD-13144 Add operatingAddress validation to Java SDK by @YegorZh in #53

Full Changelog: v0.2.5...v0.2.6

Version - 0.2.5

What's Changed

• UD-12921 Added missing transaction types by @YegorZh in #52

Full Changelog: v0.2.4...v0.2.5

Version - 0.2.4

What's Changed

• fix: Add Payment Cancelled Transaction by @YegorZh in #51

Full Changelog: v0.2.3...v0.2.4

Version - 0.2.3

What's Changed

• Transaction improvements and test adjustments by @YegorZh in #50

Full Changelog: v0.2.2...v0.2.3

Version - 0.2.2

What's Changed

• Fix long for financial fields by @YegorZh in #48
  Update to this version will be breaking and will require you to substitute the usage of Int for Long in finance related fields

Full Changelog: v0.2.1...v0.2.2

Version - 0.2.1

What's Changed

• Fix business application created naming by @YegorZh in #43
• Temporarily comment out plaid related tests by @YegorZh in #44

Full Changelog: v0.2.0...v0.2.1

Version - 0.2.0

What's Changed

• Blackduck scan fixes by @YegorZh in #39
• Second batch of test and functionality updates by @YegorZh in #40
• Version header by @YegorZh in #41
• Readme updates by @YegorZh in #42

Full Changelog: v0.1.2...v0.2.0

Version - 0.1.2

What's Changed

• Application functionality, customer functionality and test updates by @YegorZh in #35
• Correct credit account relationships by @YegorZh in #37
• Update to 0.1.2 by @YegorZh in #38

Full Changelog: v0.1.1...v0.1.2

Version - 0.1.1

What's Changed

• Fixed failing tests, renamed BIN.java to Bin.java by @YegorZh in #34

Full Changelog: v0.1.0...v0.1.1

For tips regarding the migration from 0.0.x to 0.1.x reference https://github.com/unit-finance/unit-openapi-java-sdk/releases/tag/v0.1.0

Version - 0.1.0

What's Changed

• Major update and version bump to 0.1.0 by @YegorZh in #33

Full Changelog: v0.0.7...v0.1.0

Tips for migration from 0.0.x

1. All patches were renamed to updates. E.g. PatchApplication becomes UpdateApplication
2. All data type fields are now stored as enums. If you where to use a data field for a customer you would do it as Customer.TypeEnum.INDIVIDUALCUSTOMER instead of manually writing "individualCustomer"
3. All requests now have "Request" at the end of their naming. CreateRecurringRepayment => CreateRecurringRepaymentRequest
4. Instead of having separate classes for each of the api endpoints they all grouped up in the unitApi class.

E.g.
Before refactor:

ApiClient apiClient = new ApiClient();

CreateIndividualApplication createIndividualApplication = new CreateIndividualApplication();
CreateIndividualApplicationAttributes attr = new CreateIndividualApplicationAttributes();
...

CreateApplication ca = new CreateApplication();
ca.data(new CreateApplicationData(createIndividualApplication));

CreateApplicationApi createApiClient = new CreateApplicationApi(apiClient);
UnitCreateApplicationResponse res = apiClient.execute(request);

After refactor:

ApiClient apiClient = new ApiClient();

CreateIndividualApplication createIndividualApplication = new CreateIndividualApplication();
CreateIndividualApplicationAttributes attr = new CreateIndividualApplicationAttributes();
...

CreateApplicationRequest ca = new CreateApplication();
ca.data(new CreateApplicationRequestData(createIndividualApplication));

UnitApi unitApi = new UnitApi(apiClient);
UnitCreateApplicationResponse res = unitApi.createApplication(request); 
// from here on unitApi can be used for 
// any requests as needed, e.g. unitApi.createRecurringRepayment(...);