[ADD] estate : add real estate module #1128
Open
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
|
|
artn-odoo
reviewed
Jan 20, 2026
artn-odoo
left a comment
artn-odoo
left a comment
There was a problem hiding this comment.
Nice job so far !
Just some small styling nitpicks, otherwise it's all good.
We try to always put a new line at the end of a file, this can be done automatically when you save your file in vscode if the Insert Final Newline option is activated.
csan-odoo
requested changes
Jan 21, 2026
csan-odoo
left a comment
csan-odoo
left a comment
There was a problem hiding this comment.
Great work! Just a few minor nitpicks
Add SQL constraints to ensure prices are positive and names are unique. Implement a Python constraint to prevent selling prices below 90% of the expected price.
Implement several UI improvements to enhance user experience and data visibility: - Add state-based decorations (color/bold) to the property and offer list views. - Add inline buttons to the offer list for quick 'Accept' and 'Refuse' actions. - Implement a stat button on the property type form to display a count of related offers. - Enhance the property form with statusbar, ribbons, and color-coded tags. - Update search views with custom filter domains and default groupings.
Create a new link module 'estate_account' that depends on 'estate' and 'account'.
Implement model inheritance for 'estate.property' to override 'action_sold':
- Automatically create an 'account.move' (Customer Invoice) for the property buyer.
- Add two invoice lines using the Command namespace:
1. Commission: 6% of the property selling price.
2. Administrative fees: Fixed amount of 100.00.
Create a kanban view with name, selling price, expected price, best price and tag ids and group them by type id
amahm-odoo
changed the title
csan-odoo
reviewed
Jan 22, 2026
csan-odoo
left a comment
csan-odoo
left a comment
There was a problem hiding this comment.
Perfect! Just make sure to follow the guidelines for the commit title :)
csan-odoo
requested changes
Jan 22, 2026
csan-odoo
left a comment
csan-odoo
left a comment
There was a problem hiding this comment.
Good job! Just a couple of quick changes needed.
Complete Chapter 1 of the Owl training by building a reactive Todo application: - Implement 'Playground' and 'Counter' components using 'useState' for reactivity. - Create a reusable 'Card' component featuring 'slots', 'markup' for HTML, and props validation. - Build a 'TodoList' with 'TodoItem' sub-components using 't-foreach' and dynamic attributes. - Implement Todo logic: adding tasks via 'keyup', toggling completion, and deletion via callback props. - Utilize Owl hooks: 'onMounted' and 'useRef' for DOM access (autofocus), and custom 'useAutofocus' hook.
Move all views of a model to its file, remove empty data array
csan-odoo
reviewed
Jan 26, 2026
|
|
||
| .btn-premium:active { | ||
| transform: scale(0.98); | ||
| } No newline at end of file |
There was a problem hiding this comment.
We try to always leave an empty line at the end of every file.
If you are using vscode there is an option to automatically do it which is called Insert Final Newline.
Comment on lines
+4
to
+18
| <record id="estate_property_offer_view_tree_stat" model="ir.ui.view"> | ||
| <field name="name">estate.property.offer.list.stat</field> | ||
| <field name="model">estate.property.offer</field> | ||
| <field name="arch" type="xml"> | ||
| <list string="Property Offers" editable="bottom" | ||
| decoration-danger="status == 'refused'" | ||
| decoration-success="status == 'accepted'"> | ||
| <field name="property_id"/> | ||
| <field name="price"/> | ||
| <field name="partner_id"/> | ||
| <field name="validity"/> | ||
| <field name="date_deadline"/> | ||
| </list> | ||
| </field> | ||
| </record> |
There was a problem hiding this comment.
This is not needed
Suggested change
| <record id="estate_property_offer_view_tree_stat" model="ir.ui.view"> | |
| <field name="name">estate.property.offer.list.stat</field> | |
| <field name="model">estate.property.offer</field> | |
| <field name="arch" type="xml"> | |
| <list string="Property Offers" editable="bottom" | |
| decoration-danger="status == 'refused'" | |
| decoration-success="status == 'accepted'"> | |
| <field name="property_id"/> | |
| <field name="price"/> | |
| <field name="partner_id"/> | |
| <field name="validity"/> | |
| <field name="date_deadline"/> | |
| </list> | |
| </field> | |
| </record> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
No description provided.