Skip to content

feat: allow configurable maximum active leases per property - #65

Merged
aakvatech merged 1 commit into
Aakvatech-Limited:version-15-hotfixfrom
iamtalib13:feat/max-active-leases-limit
Aug 18, 2026
Merged

feat: allow configurable maximum active leases per property#65
aakvatech merged 1 commit into
Aakvatech-Limited:version-15-hotfixfrom
iamtalib13:feat/max-active-leases-limit

Conversation

@iamtalib13

Copy link
Copy Markdown
Contributor

Summary

This PR introduces configurable active lease limits per property in PropMS, allowing properties to hold multiple active leases (defaulting to 1).

Motivation

Previously, lease validation strictly enforced a maximum of 1 active lease per property. This feature allows property managers to configure system-wise or per-property limits (e.g. 2, 3 active leases).

Type of Change

[✓] feat: A new feature

Detailed Changes

Property Management Settings (property_management_settings.json):
- Added max_active_leases (Int, Default: 1) for global system default.
Property (property.json):
-Added max_active_leases (Int, Default: 0) for property-level overrides (0 falls back to system setting).
Lease Validation (lease.py):
-Enforced max_allowed check in Lease.validate() before activating a lease.
-Formatted user-friendly error message dialog.

Verification

[✓] Tested default behavior (1 active lease limit).
[✓] Tested property-level override (2 active leases).
[✓] Verified fallback to system setting when property limit is 0.

@aakvatech
aakvatech merged commit a1bb0b2 into Aakvatech-Limited:version-15-hotfix Aug 18, 2026
2 of 3 checks passed
@github-actions

Copy link
Copy Markdown

Successfully created backport PR for version-15:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants