[ADD] estate: add an estate module #790
Closed
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
This adds an estate module that can be used to manage advertisements and offers for different real estate properties as part of the "Sever framework 101" tutorial
|
|
barracudapps
suggested changes
May 20, 2025
There was a problem hiding this comment.
Hi @mamr-odoo
Here are some tips to fit Odoo standards. Review all your code to be sure you applied the changes where it is needed!
🚀
This will clean up the estate property module from styling errors
mamr-odoo
force-pushed
the
18.0-add-estate-module-mamr
branch
from
1966ee9 to
a5040d0
Compare
Server framework 101: Chapter 4 This will add security rules to the estate module and give read, write, create and unlink permissions to the group base.group_user
Server framework 101: Chapter 5 This will add menus to the estate module and specific attributes to some of the fields
Server framework 101: Chapter 6 This will add form, list, and search views to the estate property model
Server framework 101: Chapter 7 (WIP) This will add estate property type model and will add property type, salesperson, and buyer to the estate property model
barracudapps
suggested changes
May 21, 2025
This will resolve odoo#790 (comment)
Server framework 101: Chapter 7 This will add `estate property tag` and `estate property offer` models and add them to the `estate property` model and views
This will update the column widths for the estate properties list for better readability
Server framework 101: Chapter 8 This will add to `estate.property`: - `best_price` calculated from `offer_ids` to get the highest price - `total_area` calculated from `living_area` and `garden_area` - interactions between the `garden`, `garden_area`, and `garden_orientation` and to `estate.property.offer`: - `date_deadline` and `validity` to keep track of how long the offer will stay valid
…ffer` Server framework 101: Chapter 9 This will add to `estate.property`: - `Sold` and `Cancelled` buttons to allow the users to set the update the state of properties and to `estate.property.offer`: - `Accept` and `Refuse` buttons to allow users to respond to offers
Server framework 101: Chapter 10 This will add the following constraints: - Users will have to input valid expected prices - Users won't be able to accept an offer with a price less than 0.9X the expected price - Users will have to input valid offer prices - Users won't be able to create different property tags or property types with the same names
Server framework 101: Chapter 10 This will: - Add inline properties list to property type - Add widget for property state - Add ordering to the lists - Add conditional display to the fields - Add colors to the property and offer lists based on their status - Add search by living area greater than or equal for properties - Add an "offers" smart button to property type
Server framework 101: Chapter 12 This will add a list of the available (new, offer received) to the user view
Server framework 101: Chapter 13 This will add an `estate_account` module which will automatically create the invoice for the buyer of a property when it is marked as sold [ADD] estate: add module for invoicing customers after purchase Server framework 101: Chapter 13 This will add an `estate_account` module which will automatically create the invoice for the buyer of a property when it is marked as sold
mamr-odoo
force-pushed
the
18.0-add-estate-module-mamr
branch
from
b59a51f to
3e72a2c
Compare
Server framework 101: Chapter 14 This will add a kanban view grouped by property type
This will replace the deprecated `kanban-box` template with the `card` template
This will remove the invisible fields from the estate forms because they are not needed
mamr-odoo
force-pushed
the
18.0-add-estate-module-mamr
branch
from
6693444 to
23ebd9a
Compare
| property_type_id = fields.Many2one('estate.property.type', string='Property Type') | ||
| description = fields.Text('Description') | ||
| postcode = fields.Char('Postcode') | ||
| date_availability = fields.Date('Available From', default=fields.Date.today() + relativedelta(months=3), copy=False) |
There was a problem hiding this comment.
Suggested change
| date_availability = fields.Date('Available From', default=fields.Date.today() + relativedelta(months=3), copy=False) | |
| date_availability = fields.Date( | |
| 'Available From', | |
| default=lambda self: fields.Date.today() + relativedelta(months=3), | |
| copy=False | |
| ) |
As this value should be recomputed, prefer using a lambda function. The current way stores the value at the server start.
|
Good job mate! 🚀 |
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 adds an estate module that can be used to manage advertisements and offers for different real estate properties as part of the "Sever framework 101" tutorial