[ADD] estate: implement core real estate property management module #758
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Core Functionality: - Created base models for property listings with fields for pricing, descriptions , and status tracking - Implemented property type categorization (House, Apartment etc.) - Added tagging system for property characteristics (Cozy, Renovated etc.) - Developed offer management system to track buyer proposals Technical Implementation: 1. Models: - estate.property (main listing model) - estate.property.type (categorization) - estate.property.tag (characteristics) - estate.property.offer (purchase offers) 2. Relationships: - Many2one: Property → Type, Buyer, Salesperson - Many2many: Property ↔ Tags - One2many: Property → Offers 3. Security: - Configured access rights for all models - Set appropriate permissions for CRUD operations 4. UI/UX: - Custom list view with key property attributes - Detailed form view with tabbed interface - Advanced search with filters and grouping - Intuitive menu structure 5. Business Logic: - Default values (salesperson = current user) - Field constraints (read-only selling price) - Non-copyable fields (availability date) task-001 (Chapter 1–7 Odoo 18 Developer Tutorial)
|
|
…arameter SQL Constraints: - Add CHECK(expected_price > 0) to ensure strictly positive expected prices. - Add CHECK(selling_price >= 0) for non-negative selling prices. - Ensure price > 0 for offers via SQL constraint. - Enforce unique names for property tags and types with UNIQUE(name). Python Constraint: - Add @api.constrains to validate selling price ≥ 90% of expected price. Fixes: - Correct typo in selling_price field parameter (readOnly → readonly). - Cleanup existing invalid data (e.g., non-positive prices) to apply constraints.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Core Functionality:
Technical Implementation:
Models:
Relationships:
Security:
UI/UX:
Business Logic:
task-001 (Chapter 1–7 Odoo 18 Developer Tutorial)