Draft
Conversation
|
|
kapat-odoo
changed the title
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
from
7ff9e78 to
ce86a09
Compare
bit-odoo
reviewed
Feb 10, 2026
bit-odoo
left a comment
bit-odoo
left a comment
There was a problem hiding this comment.
Hello @kapat-odoo
Can you please improve all your commit messages and PR messages?
Thanks
estate/README.rst
Outdated
| @@ -0,0 +1 @@ | |||
| Real Estate Module README file No newline at end of file | |||
Author
There was a problem hiding this comment.
As previously i was using pylint_odoo instead of ruff, so in that it was bugging me with "add README.rst" as a requirement for every module so i added that but i now understand that it is not necessary so i would remove it in my next commit.
edit: I have removed the README.rst in commit odoo-dev@df16749
Thank You.
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
from
ce86a09 to
9afc696
Compare
kapat-odoo
changed the title
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
3 times, most recently
from
6c4f6ab to
70f51f7
Compare
Initialized the 'estate' module and made it installable in Odoo. This commit bootstraps the custom estate module and sets up the minimal structure required by Odoo to load and install a new application. Created the module structure 'estate' inside the tutorials directory, configured basic module metadata. Restarted the server to load the module, then verified it is visible in the Apps menu. Chapter 1 and 2 of the documentation.
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
2 times, most recently
from
55054b5 to
8aa5657
Compare
Added the 'estate.property' model with all required fields and enforce field constraints. This commit implements the core data structure for the Real Estate module, ensuring properties have the appropriate attributes stored in the database and enforcing essential constraints to maintain data quality. These fields serve as the foundation for later views, business logic, and workflows built on top of the model. Defined fields such as name, description, postcode, date_availability, expected_price, selling_price, bedrooms, living_area, facades, garage, garden, garden_area, garden_orientation as per Chapter 3 of documentation.
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
from
8aa5657 to
e009b7a
Compare
Implemented security access control to the estate module to remove the missing access rules warning and allow proper user access. Without explicit access rules, Odoo blocks access to the new models and logs a warning about missing security rules. Adding these ACL entries ensures that regular users in the 'base.group_user' group can interact with the estate models as intended, providing a baseline security setup for the module. As per discussed in Chapter 4 provided permission to base.group_user to read, write, create and unlink.
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
from
e009b7a to
6e5ea80
Compare
…odule. Made the estate module interactive and visible in root menu of Odoo, also implemented action menus with different menu items and hierarchy. Now the listings of property appears in list view and while creating a new property it opens in form view while also making changes to fields to make them have default values and made sure they cannot be copied. As per Chapter 5 of Documentation.
kapat-odoo
force-pushed
the
19.0-tutorial-kapat
branch
from
bcb4c51 to
2705305
Compare
…h search. Added list and form views for estate.property along with search and custom filters like (to check availability and Group by Postcode). This commit replaces the default auto-generated views with list view for providing a quick glance at all important attributes related to the property and implemented better custom form view (which now also features 'state' selection which will be further useful in checking functionality of the custom filter). Along with that also added fields in search so that it can provide user to choose which particular attribute the search should query, also implemented custom filter for checking if the property is available by looking up the state and a 'Group By Postcode'. As per discussed in Chapter 6.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Initialized the 'estate' module and made it installable in Odoo.
This commit bootstraps the custom estate module and sets up the minimal
structure required by Odoo to load and install a new application.
Created the module structure 'estate' inside the tutorials directory,
configured basic module metadata. Restarted the server
to load the module, then verified it is visible in the Apps menu.