[ADD] real_estate: add complete real estate management module #839
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 the initial file architecture for the real_estate module, including the necessary directories and manifest file. Implemented the estate.property model using Odoo ORM to define the database table structure required for storing property-related data. This commit sets up the foundation for the module, making it ready for further development of features such as property management, views, and business logic.
Added access control rules for the real_estate module to restrict and manage user permissions. Implemented list and form views for the estate.property model, including search functionality. Customized list and form views with additional fields. These enhancements provide the necessary security and user interface elements..
…buttons - Linked models using One2many, Many2one, and Many2many fields - Added computed fields like best_offer and offer_deadline - Implemented onchange methods for dynamic field updates - Created type='object' buttons: • Sold / Cancelled on properties • Accept / Refuse on offers
…ttons - Added inline views, statusbar, widget options - Set SQL & Python constraints for data validity - Defined default ordering for all models - Conditional button visibility & field behaviors - Editable/color-coded list views with decorations - Stat button for offer count on property type
|
|
…ration - Enforced business rules for property deletion and offer validation - Linked available properties to users via domain and UI integration - Introduced estate_account as a modular extension for invoicing with commission and fixed administrative charges
metu-odoo
force-pushed
the
18.0-training-metu
branch
from
ab10458 to
7a4879a
Compare
maad-odoo
reviewed
Jul 10, 2025
There was a problem hiding this comment.
First pass ... 🚀 ,
Not in depth technical review.
- The PR title is not appropriate. The PR title should be describe more about why the
PR is made on the first place. - The diff contains alot of unnecessary diff.
Please adapt this change and do not leave unnecesary diffs 🙏
Thank you 🙂
Contains a lot of unnecessary diff which is not required.
| @@ -0,0 +1 @@ | |||
| from . import models | |||
There was a problem hiding this comment.
Missing licensing info
Applies throughout the diff
There was a problem hiding this comment.
-- coding: utf-8 --
Part of Odoo. See LICENSE file for full copyright and licensing details.
sir do you mean this ?
There was a problem hiding this comment.
runbot is failing because of these lines
There was a problem hiding this comment.
it will be failing because of encode declaration and not for the licensing part.
you can remove the encoding part and keep the licensing part
metu-odoo
changed the title
metu-odoo
changed the title
metu-odoo
force-pushed
the
18.0-training-metu
branch
3 times, most recently
from
64b8a3e to
5c94fc5
Compare
|
done!
…On Thu, Jul 10, 2025 at 6:06 PM maad-odoo ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In estate_account/__init__.py
<#839 (comment)>:
> @@ -0,0 +1 @@
+from . import models
it will be failing because of encode declaration and not for the licensing
part.
you can remove the encoding part and keep the licensing part
—
Reply to this email directly, view it on GitHub
<#839 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BPDPFYG7ZHG7DOX5TZIR6LL3HZM53AVCNFSM6AAAAACBDEHN7WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTAMBVGUYDINRVG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
- Renamed methods and variables to follow naming conventions - Reviewed and aligned code with Odoo coding standards - Studied and applied key security practices: - Avoided unsafe public methods - Prevented direct SQL and ensured ORM usage - Avoided unsafe attribute access patterns
metu-odoo
force-pushed
the
18.0-training-metu
branch
from
5c94fc5 to
b02961b
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.
This branch introduces a complete Real Estate management module to handle
property listings, offers, access control, invoicing, and website integration.
Key Features:
Property Management: Configure and manage estate properties with clean form,
list, and kanban views.
Offer Handling: Enable offer submission with business validations and acceptance
workflows.
Access Control: Define model-level access and permissions for real estate roles.
Website Integration: Display listings and allow users to submit offers online.
Accounting: Seamlessly integrate with invoicing through the
estate_account module
Standards Compliance: Includes test coverage and follows Odoo best practices.
This module offers an end-to-end Real Estate solution within the Odoo ecosystem.