Skip to content

Conversation

@Mohamed-Khaled308
Copy link

@Mohamed-Khaled308 Mohamed-Khaled308 commented Oct 20, 2025

Added new Modules: estate{_account}

  1. Estate Module:
  • Lets you list and sell estate properties.
  • Add property details like type, size, rooms, garage, and price.
  • Receive offers — the property status updates automatically.
  • Review offers (sorted from highest to lowest) and accept or reject them.
  • View properties in List, Kanban, or Form views.
  • By default, shows only properties with New or Offer Received status.
  • Once a property is Sold, Cancelled, or Offer Accepted, the offers list becomes read-only.
  1. Estate Account Module
  • It is built on both estate and account modules.
  • When a property is sold, it automatically creates an invoice in the accounting app.

@robodoo
Copy link

robodoo commented Oct 20, 2025

Pull request status dashboard

@Mohamed-Khaled308 Mohamed-Khaled308 changed the title 19.0 onboarding moaln MOALN Onboarding Oct 20, 2025
@Mathilde411 Mathilde411 requested a review from alan-odoo October 20, 2025 12:00
Copy link

@alan-odoo alan-odoo left a comment

Choose a reason for hiding this comment

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

Hi @Mohamed-Khaled308 👋,

The naming of the view and the pip8 are respected almost everywhere. Be careful to write only required code, as we are a lot to work on odoo the code base can quickly become huge.

Don't forget to add a title and a description to your PR. The title must have same structure than a commit -> [ADD/IMP/FIX....] app: what the pr is for. About the description, it must mainly explain why you did the PR and not how you did it.

You did a great job 😃!

Copy link

@alan-odoo alan-odoo left a comment

Choose a reason for hiding this comment

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

Hi @Mohamed-Khaled308 👋,

I did a review of your PR. Here are some comments about the pep8 and the code simplification.

Thanks for your work 😃

Comment on lines 1 to 5
from . import estate_property
from . import estate_property_type
from . import estate_property_tag
from . import estate_property_offer
from . import res_users

Choose a reason for hiding this comment

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

Should be sorted alphabetically. That's in the pep8 . It's the official documentation to write clean python 😃

Suggested change
from . import estate_property
from . import estate_property_type
from . import estate_property_tag
from . import estate_property_offer
from . import res_users
from . import estate_property
from . import estate_property_offer
from . import estate_property_tag
from . import estate_property_type
from . import res_users

Copy link
Author

Choose a reason for hiding this comment

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

Is there any automatic way that checks these format errors and fixes them maybe?
I am using pycharm now btw.

Choose a reason for hiding this comment

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

Maybe you can do as explain here? I've never tried it.

@alan-odoo
Copy link

Hi @Mohamed-Khaled308 😃,

You should also add a title and a description to your PR. The title must have the same structure than a commit title -> [ADD/IMP/FIX...] app: the purpose of the pr (must start by a verb). And for the description, it must mainly explain why the PR is doing this and not how.

Cheers !

@Mohamed-Khaled308 Mohamed-Khaled308 changed the title MOALN Onboarding [ADD] estate{_account}: added estate{_account} moduels - MOALN Oct 28, 2025
Copy link

@alan-odoo alan-odoo left a comment

Choose a reason for hiding this comment

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

Hi @Mohamed-Khaled308,

Thanks for the updates 😃. Just small changes to do, they are not a priority.

The description is quite good. For the title, you could do two small corrections. The pentagram at the end of it is not required. And you don't need to specify twice the modules impacted by you changes. So your title should look like "[ADD] estate{_account}: added modules"

Cheers !

<field name="validity" string="Validity (days)"/>
<field name="date_deadline" string="Deadline"/>
<button name="action_accept_offer" type="object" icon="fa-check"
invisible="status or property_state in['offer_accepted', 'sold', 'cancelled']"/>

Choose a reason for hiding this comment

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

You forgot the space here 😅.

<button name="action_accept_offer" type="object" icon="fa-check"
invisible="status or property_state in['offer_accepted', 'sold', 'cancelled']"/>
<button name="action_refuse_offer" type="object" icon="fa-close"
invisible="status or property_state in['offer_accepted', 'sold', 'cancelled']"/>

Choose a reason for hiding this comment

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

Same here.

Comment on lines 1 to 5
from . import estate_property
from . import estate_property_type
from . import estate_property_tag
from . import estate_property_offer
from . import res_users

Choose a reason for hiding this comment

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

Maybe you can do as explain here? I've never tried it.

@api.depends("offer_ids")
def _compute_offer_count(self):
for type in self:
type.offer_count = len(type.offer_ids or [])

Choose a reason for hiding this comment

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

[] shouldn't be necessary as offer_ids will always be a list even if there is no records.

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