-
Notifications
You must be signed in to change notification settings - Fork 2.3k
[ADD] estate,*: added real estate module #846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
zadh-odoo
wants to merge
6
commits into
odoo:18.0
Choose a base branch
from
odoo-dev:18.0-training-zadh
base: 18.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+747
−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
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
824ce8f
to
756fc9e
Compare
maad-odoo
reviewed
Jul 10, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick pass.
There are of unwanted diff in the code base.
Also the PR message is not appropriate, please adapt this as well.
Comment on lines
8
to
+10
view_mode = fields.Selection(selection_add=[ | ||
('gallery', "Awesome Gallery") | ||
], ondelete={'gallery': 'cascade'}) | ||
], ondelete={'gallery': 'cascade'}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why this change ?
58239c2
to
9066f95
Compare
…module data - Added security groups, access rights, and record rules to both estate and estate_account modules. - Defined and updated security XML files: created agent and manager groups, set appropriate access permissions for each model. - Added record rules to restrict agents to their own properties and ensure managers have global access. - Populated initial group and access data using XML data files. - Updated module manifests to reference new security and data files. - estate_account inherits and respects estate security, and applied access rules to accounting-related features. - Create demo records for estate properties and link them to the appropriate property types. These records will be used for testing and demonstration purposes. - Add demo offers related to the demo properties, ensuring each offer is associated with a valid property and partner. - Add initial master data for property types, including Residential, Commercial, Industrial, and Land. This provides the base categories for estate properties.
9066f95
to
4562c04
Compare
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.
*=estate_account