[ADD] estate: add real estate module (framework 101 tutorial) #1077
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
|
|
robal-odoo
force-pushed
the
19.0-estate-tutorial-robal
branch
from
924f90b to
0af92ad
Compare
robal-odoo
changed the title
Framework 101 tutorial: chapter 2 - Create skeleton structure for the new real estate module
- Add ".vscode" directory to .gitignore
Framework 101 tutorial: chapter 3 - Create a new model "estate.property" for real estate properties to sell
Framework 101 tutorial: chapter 4 - Create model access csv file - Add a basic access rule to allow access for users of group "base.group_user" with all permissions
Framework 101 tutorial: chapter 5 - Add basic UI menus for the estate module - Add reserved fields "active" and "state" to the "estate.property" model - Configure fields of the "estate.property" model: readonly, default values and record duplication
… models Framework 101 tutorial: chapter 6 - Add xml definitions for the estate properties' form and list views to improve UI - Renamed some labels in the models, menus and actions to improve UI
- Renamed external ids for menus and actions to more accuratly reflect what they actually are
Framework 101 tutorial: chapter 7 - Add view and model definitions for new models: tags, property types and offers - Add basic access rules for these new models (all permissions for now) - Update the estate property model with new related fields - Estate properties can now be tagged - Estate properties now have a type - Estate properties can now have one or multiple offers
First pass of ruff linter
Second pass of ruff linter
Framework 101 tutorial: chapter 8 - Estate properties now have computed fields to display the best offer (i.e. best price) and the total area (i.e. sum of living area + garden) - Default values are set or cleared when clicking the garden checkbox - Introduced validity period fields for offers
…ting refusing offers Framework 101 tutorial: chapter 9 - Add actions for selling and cancelling estate properties - Add actions for accepting and refusing offers
robal-odoo
force-pushed
the
19.0-estate-tutorial-robal
branch
from
cab625c to
d8993d0
Compare
According to the reference screenshots, the property form view is not supposed to display the property's state, so we remove it.
…g a previously accepted offer Since accepting an offer sets the buyer and selling price on the estate property, we clear those fields when a previously accepted offer is refused.
The Github CI gives warnings about buttons with icons and no text. So, we add some text to fix this.
Framework 101 tutorial: chapter 10 - Add contraints on estate property, tag and types models to ensure data consistency - Tag and type names must be unique - Offer prices must be strictly positive - An estate property's selling price must be equal to or greater than zero. Note that this price is zero when no offer has been accepted for the property. - An estate property's expected price must be strictly greater than zero. - An estate property's selling price cannot be lower than 90 percent of its expected price. Effectively, this means that offers that have too low of a price cannot be accepted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.