Skip to content

Conversation

@hossamelgendy1
Copy link

The R&D training real estate module

initial structure of the new estate module
@robodoo
Copy link

robodoo commented Jan 20, 2026

Pull request status dashboard

adding config file and a script to run before commits to check formatting
Adding definition of estate_property model along with its attributes
Adding author and license to fix GitHub CI/tutorials action
Adding read access right for base.group_user
rename model to use . instead of _ to follow naming convention
allow other access patterns on estate.property to be able to create a property
Adding the form view with basic functionality for estate.property along with menus with the single resource we have so far.
Copy link

@plha-odoo plha-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job for the quality of the code, for the styling and for using the proper commit message titles convention !
a few comments :

  • 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.
  • don't forget to add your ruff.toml and ruff.sh files in a gitignore file so it's not pushed in your remote branch

following convention of having a new at the end of every file
@hossamelgendy1
Copy link
Author

Good job for the quality of the code, for the styling and for using the proper commit message titles convention ! a few comments :

  • 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.
  • don't forget to add your ruff.toml and ruff.sh files in a gitignore file so it's not pushed in your remote branch

Thanks for the feedback!

  • Done with the first point.. nice to know the convention and the vscode feature!
  • For the second point, yeah makes sense, but should I add them in my local .git/info/exclude to avoid cluttering the remote .gitignore file with developer-specific files? or .gitignore is fine?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants