- Add a new Rhai example showcasing complete payment flow
for company registration. This includes company creation,
payment record creation, successful payment processing,
status updates, and handling failed and refunded payments.
- Add new example demonstrating payment integration in Rhai
scripting. This example showcases the usage of various
payment status methods and verifies data from the database
after processing payments.
- Add new examples to Cargo.toml to facilitate building and
running the examples. This makes it easier to integrate
and test payment functionality using Rhai scripting.
- Add `signature_data` field to `ContractSigner` to store base64
encoded signature image data. Allows for storing visual
signatures alongside electronic ones.
- Implement `sign` method for `ContractSigner` to handle signing
with optional signature data and comments. Improves the
flexibility and expressiveness of the signing process.
- Add Rhai functions for signature management, including signing
with/without data and clearing signature data. Extends the
Rhai scripting capabilities for contract management.
- Add comprehensive unit tests to cover the new signature
functionality. Ensures correctness and robustness of the
implementation.
- Update examples to demonstrate the new signature functionality.
Provides clear usage examples for developers.
- Added `last_reminder_mail_sent_at` field to track reminder
timestamps.
- Implemented `can_send_reminder` to check if a reminder can be
sent based on a 30-minute cooldown.
- Added `reminder_cooldown_remaining` to get remaining cooldown
time.
- Added `mark_reminder_sent` to update reminder timestamp.
- Added example demonstrating reminder functionality in
`legal_contract_example.rs`.
- Added tests for reminder functionality in
`test_reminder_functionality.rs`.
- Updated Rhai scripts to include reminder-related functions and
tests.
- Improved formatting and clarity in example code.
- Added `to_json` method to serialize Event to JSON string.
- Added `from_json` method to deserialize Event from JSON string.
- This allows for easier data exchange and persistence.
- Add EventStatus enum to represent event states (Draft, Published, Cancelled).
- Extend Event model with color, category, reminder, timezone, created_by, all_day and is_recurring fields.
- Add color and description fields to Calendar model.
- Enhance calendar example to demonstrate new features, including event status changes, and detailed calendar information.
- Improve example output for clarity and comprehensiveness.
- Add owner_id and is_public fields to Calendar model for enhanced management.
2025-05-28 13:09:05,630 - INFO - Commit message copied to clipboard.
- Add user creation and management to the calendar example.
- Integrate user IDs into attendees for improved data integrity.
- Improve event manipulation by adding and removing attendees by ID.
- Enhance calendar example to demonstrate event and calendar retrieval.
- Enhance the calendar example with database storage for events.
- Modify the calendar example to manage events by ID instead of title.
- Ensure all model types always have a primary key index entry.
- Simplify `get_all()` implementation by relying on primary key index.
- Remove redundant code in `get_all()` for finding all object IDs.
- Improve error handling and clarity in database operations.
- Add `Activity` model to track proposal creation and voting.
- Include `ActivityType` enum for different activity types.
- Improve `Proposal` model to record voting with comments.
- Refactor `models/governance` module for better organization.
- Added a comprehensive example demonstrating governance activity tracking.
- Created `GovernanceActivity` model to record governance events.
- Improved error handling in `OurDB::get_all` to gracefully handle deserialization failures.
