- Use DeepSeek API (api.deepseek.com) with openai-go SDK
- Replace OPENAI_MODEL env var with DEEPSEEK_MODEL
- Default model: deepseek-v4-pro
- API key read from DEEPSEEK_API_KEY env var
Redesigned the invoice PDF with a more modern, modular layout. Updated
colors, spacing, and section organization for better readability and
visual appeal. Added a summary block, improved table formatting, and
refined header/footer presentation. Also updated dependencies in go.mod
and go.sum to support new features.
Refactored the invoice PDF generation to use a modular, visually
improved
layout. Extracted header, details, items, payments, summary, and notes
sections into dedicated functions for clarity and maintainability.
Introduced color constants and improved table formatting for better
readability. Updated labels and formatting to enhance the overall
appearance and user experience of generated invoices.
Refactored payment link creation to ensure booking_id is set in both the
PaymentLink and PaymentIntent metadata. Extracted parameter building
logic
into a helper for improved testability. Added a unit test to verify
metadata propagation.
Introduce backend and frontend support for generating Stripe payment
links
for outstanding booking balances. Adds a new POST endpoint to create
payment
links, updates booking view to include a Stripe button, and integrates
error handling and feedback for payment link creation. Refactors view
models and templates to support the new feature.
Eliminated all references to the Stripe Connect account configuration
and
option handling. This includes removing the related environment
variable,
config struct field, client option, and usage in Stripe client setup.
Stripe integration now only uses the main secret key and webhook secret.
Refactors main.go to streamline context and logger initialization.
Moves signal handling directly into main, sets up a base logger for
early errors, and updates error handling to use structured logging.
No functional changes to application logic.
This commit standardizes the naming of identifier and API key fields
across the codebase to use consistent camel case (e.g., `ID`, `APIKey`,
`DatabaseURL`). This includes updates to struct fields, method names,
function parameters, and environment variable references. The changes
improve code clarity and maintainability by reducing ambiguity and
aligning with Go naming conventions. No functional behavior is changed.
Introduce slog-based structured logging throughout the booking service
and
server handlers. Add configurable log level via LOG_LEVEL environment
variable. Replace legacy log usage with slog and propagate logger to
booking service for improved observability.
- Update BookingAgentParser to utilize OpenAI's client for parsing booking data.
- Remove base URL dependency and streamline the initialization process.
- Introduce ResponseData struct to define expected JSON structure from the LLM.
- Add unit tests for BookingAgentParser to validate parsing logic and expected output.
### TL;DR
Implemented embedded file system for static assets using Go's `embed` package.
### What changed?
- Created a new `assets.go` file to define an embedded filesystem for static assets
- Moved all static assets (HTML, icons, images, JS) under a nested `assets` directory
- Updated PDF generation to use the embedded filesystem when parsing HTML templates
- Modified main application to use the embedded filesystem for serving static files
- Added logging statements for invoice generation
### How to test?
1. Run the application and verify static assets are served correctly
2. Generate a PDF invoice and confirm it renders properly
3. Check that all HTML error pages (400, 401, 403, 404, 500) are accessible
4. Verify images and icons load correctly throughout the application
### Why make this change?
Using an embedded filesystem ensures all static assets are compiled into the binary, making deployment simpler and more reliable. This eliminates the need to manage separate asset files and ensures the application has all required resources available at runtime.
### TL;DR
Enhanced invoice generation with improved formatting and Euro symbol display
### What changed?
- Added Euro symbol (€) to monetary values in the invoice template
- Implemented new invoice data structure with dedicated types for lines and payments
- Created ToInvoice method to properly format booking data for invoice generation
- Added HTML template parsing and rendering functionality
- Improved date formatting for consistency
- Added new API endpoint for booking creation
### How to test?
1. Create a new booking through the API
2. Navigate to the PDF generation endpoint
3. Verify that monetary values display with Euro symbol
4. Check that dates are properly formatted
5. Confirm that payment history and totals are correctly calculated
6. Validate that the generated HTML maintains proper formatting
### Why make this change?
To improve invoice readability and consistency by standardizing monetary value display and providing better data structure for invoice generation. This change also makes the system more maintainable by separating concerns between data transformation and presentation.
