Releases: lucrise-llc/azul-ts
Releases · lucrise-llc/azul-ts
v2.0.0
2.0.0 (2025-01-29)
Bug Fixes
- azul-api: typing & fix test (bad1568)
Features
- core: enhance DataVault integration, certificate handling, and test suite (#12) (1e8519c)
- export data-vault & process payment types (0a8c6d7)
BREAKING CHANGES
-
core: This is not compatible with our latest release.
-
feat(config): add certificate handling and configuration
- Added new
config.ts
for centralized configuration management - Added
check-certificates.ts
example for certificate validation - Updated API client to support certificate configuration
- Enhanced
.env.sample
with certificate-related variables
This improves certificate handling and provides better examples for users implementing certificate-based authentication.
- refactor(data-vault): improve schema validation and type safety
- Update DataVault schemas to include required fields (channel, store)
- Add proper type definitions for Create and Delete operations
- Improve ProcessPaymentSchema to handle DataVault tokens correctly
- Split into BasePaymentSchema, CardPaymentSchema and TokenPaymentSchema
- Add proper validation for token-based payments
- Update field constraints (altMerchantName: 25 chars, dataVaultToken: 36 chars)
- Remove DataVaultTransaction enum in favor of literal types
- Fix documentation comments and typos
- refactor(tests): standardize test assertions and card handling
- Add test card fixtures with consistent test data
- Create utility functions for common test assertions:
- expectSuccessfulPayment
- expectSuccessfulVerification
- expectSuccessfulVaultResponse
- expectSuccessfulVoid
- expectValidationError
- expectOrderIds
- Update all integration tests to use shared test cards and assertions
- Add proper type guards and response type definitions
- Handle temporary system errors (91) gracefully with warnings
- Improve test descriptions and organization
- feat(examples): add simple payment workflow demonstration
- Create new example script for end-to-end payment processing
- Demonstrate key Azul API workflows: hold, post, and verification
- Include environment configuration logging and error handling
- Use test card fixture and random order ID for realistic scenario
- refactor(tests): use centralized config for Azul API instance
- Replace hardcoded environment variables with CONFIG import
- Leverage centralized configuration for test API instance setup
- Improve consistency with recent configuration management changes
- test(certificates): remove redundant invalid certificate test
- Remove test case for non-PEM certificate file
- Simplify test suite by eliminating redundant error handling scenario
- Maintain core certificate error testing logic
- docs(readme): update Azul API and page configuration examples
- Add environment and channel configuration options
- Clarify certificate and key input methods
- Update payment method example with more detailed parameters
- Improve documentation for API initialization and usage