18.0 training kums #847
Draft
18.0 training kums #847
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.
This commit introduces the initial version of the estate module as part of the Odoo 18 developer tutorial. The module includes basic models, access rights, security rules, and simple form and tree views for managing real estate properties. The purpose of this change is to set up a foundational structure for the module. It follows the official tutorial steps to demonstrate Odoo’s ORM, security mechanisms, and view definitions. Adding proper access control ensures that only authorized users can interact with the module. The initial UI provides the groundwork for extending functionality later. This is part of a learning exercise to understand Odoo’s server framework and how to implement a feature-rich module following best practices.
-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
Added model and view inheritance for extending existing functionality., Implemented interaction with external modules using dependencies., Updated estate module to demonstrate cross-module field access and method calls.
|
|
- Cleaned up code to meet linting and CI style standards.
Implemented cross-module field access and method calls to demonstrate interaction with other modules., Cleaned codebase to fix linter errors and improve readability.
kums-odoo
force-pushed
the
18.0-training-kums
branch
from
bc7078f to
9aa35ca
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 PR adds demo data to the estate module as per the Odoo Estate tutorial.
Features:
-Estate module initialization and configuration
-Property model definition with key fields
-Basic list and form views
-Menu and action setup for navigation
-Implemented Inheritance