[ADD] estate: added real estate module #846
Draft
+647
−1
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
- Created new 'estate' module. - Added base model 'estate.property' with fields mentioned in exercise. - Set up module structure. - Set 'name' and 'expected_price' as required fields.
- Added security rules for the estate. - Registered the security files in __manifest__.py to enable permission. - Created menu items for the estate.property model. - Added XML files for actions and menus. - Added basic views for the estate.property model, including form and list views. - Set default values for fields, made certain fields readonly.
-Created new models for property offers,tags and types. -Defined relation between these data models for accessing data across the model. -Created new views for property types,property tags. -Defined action on button click , created computed fields .
- Added SQL constraints to ensure: - Property expected price is strictly positive - Property selling price is positive - Offer price is strictly positive - Property tag name and property type name are unique - Added Python constraint to prevent selling price from being set below 90% of expected price - Changes in UI: - Added inline list view for properties on property type form - Used statusbar widget for property state display - Defined default ordering for models and enabled manual ordering for property types via sequence field - Applied widget options to restrict creation/editing of property types from property form
|
|
zadh-odoo
force-pushed
the
18.0-training-zadh
branch
3 times, most recently
from
d7e6602 to
824ce8f
Compare
…module Applied model and view inheritance patterns to extend core functionality Enabled interactions between modules for enhanced business workflows Updated business logic to support new integration features
zadh-odoo
force-pushed
the
18.0-training-zadh
branch
from
824ce8f to
756fc9e
Compare
zadh-odoo
changed the title
maad-odoo
reviewed
Jul 10, 2025
Comment on lines
8
to
+10
| view_mode = fields.Selection(selection_add=[ | ||
| ('gallery', "Awesome Gallery") | ||
| ], ondelete={'gallery': 'cascade'}) | ||
| ], ondelete={'gallery': 'cascade'}) |
| @@ -0,0 +1 @@ | |||
| from . import models | |||
| 'author': "Dhruvrajsinh Zala (zadh)", | ||
| 'installable': True, | ||
| 'application': True, | ||
| 'data': ['security/ir.model.access.csv', 'views/estate_property_views.xml', 'views/estate_property_offers.xml', 'views/estate_property_type_views.xml', 'views/estate_property_tags.xml', 'views/res_users_views.xml', 'views/estate_menus.xml'], |
Comment on lines
+26
to
+27
| description = fields.Text() | ||
| postcode = fields.Char() |
Comment on lines
+33
to
+35
| expected_price = fields.Float(required=True) | ||
| selling_price = fields.Float(readonly=True, copy=False) | ||
| bedrooms = fields.Integer(default=2) |
There was a problem hiding this comment.
Same missing the string property is missing in the field definition
Comment on lines
+15
to
+24
| <field name="price"/> | ||
| <field name="partner_id"/> | ||
| <field name="validity"/> | ||
| <field name="date_deadline"/> | ||
| <button name="action_accept_offer" type="object" title="Accept" icon="fa-check" invisible="status in ( | ||
| 'accepted','refused')"/> | ||
| <button name="action_refuse_offer" type="object" title="Refuse" icon="fa-times" invisible="status in ( | ||
| 'accepted','refused')"/> | ||
| </list> | ||
| </field> |
Comment on lines
+6
to
+10
| </record> | ||
|
|
||
|
|
||
|
|
||
|
|
Comment on lines
+7
to
+10
|
|
||
|
|
||
|
|
||
|
|
Comment on lines
+14
to
+16
| journal = self.env["account.journal"].search( | ||
| [("type", "=", "sale")], limit=1 | ||
| ) |
There was a problem hiding this comment.
Is searching inside a for loop a good idea ?
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.
This PR adds demo data to the estate module as per the Odoo Estate tutorial.
Features:
-Estate module initialization and configuration
-Property model definition with key fields
-Basic list and form views
-Menu and action setup for navigation
-Implemented Inheritance
-Creates Invoice on Property Sell