Skip to content

19.0: Onboarding bepro - #1365

Open
bepro-odoo wants to merge 37 commits into
odoo:19.0from
odoo-dev:19.0-onboarding-bepro
Open

19.0: Onboarding bepro#1365
bepro-odoo wants to merge 37 commits into
odoo:19.0from
odoo-dev:19.0-onboarding-bepro

Conversation

@bepro-odoo

Copy link
Copy Markdown

No description provided.

@robodoo

robodoo commented Jul 20, 2026

Copy link
Copy Markdown

Pull request status dashboard

@bepro-odoo bepro-odoo changed the title Onboarding bepro (19.0) 19.0: Onboarding bepro Jul 20, 2026
@bepro-odoo bepro-odoo closed this Jul 20, 2026
@bepro-odoo bepro-odoo reopened this Jul 20, 2026
@bepro-odoo
bepro-odoo requested a review from SaddemAmine July 20, 2026 13:20
@bepro-odoo bepro-odoo assigned bepro-odoo and unassigned SaddemAmine Jul 20, 2026
@SaddemAmine
SaddemAmine requested a review from YassinWalid July 22, 2026 07:25
@bepro-odoo
bepro-odoo force-pushed the 19.0-onboarding-bepro branch 4 times, most recently from bcb799c to a33e72e Compare July 22, 2026 15:01
@bepro-odoo
bepro-odoo force-pushed the 19.0-onboarding-bepro branch from a33e72e to 64cd738 Compare July 22, 2026 15:18

@YassinWalid YassinWalid left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks for the impressive work. I have left a few comments in the PR, so feel free to check them (and if you don't agree with sth we can always discuss it, since in many cases there is no "absolute truth". Please also check the coding guidelines below.

Patterns for names and ids for records in xml files:
please check this link: https://www.odoo.com/documentation/19.0/contributing/development/coding_guidelines.html#xml-ids-and-naming

Also, please split your views into one file per model, so they can be found easier.

Comment thread .vscode/tutorials.code-workspace Outdated
Comment thread estate/models/__init__.py Outdated
Comment thread estate/models/property.py Outdated
Comment thread estate/models/property.py Outdated
Comment thread estate/models/property.py

description = fields.Text(string='description')
postcode = fields.Char(string='postcode')
date_availability = fields.Date(string='Available from', default=lambda _: fields.Date.add(fields.Date.today(), months=3), copy=False)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggested change
date_availability = fields.Date(string='Available from', default=lambda _: fields.Date.add(fields.Date.today(), months=3), copy=False)
date_availability = fields.Date(string='Available from', default=fields.Date.add(fields.Date.today(), months=3), copy=False)

We don't need the lambda here. We could just put the value as it is.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I tested the approach without lambda and fieldtype datetime. The form value is stuck at a datetime around startup of odoo server, meaning that the default value is generated once and reused as default. The purpose of the field is to have a date set 3 months into the future at point of record creation, implying the date must be calculated at that point in time, hence the lambda is required.

Info @SaddemAmine

Comment thread estate/views/estate_property_views.xml Outdated
<form string="Estate Property Type">
<sheet>
<div class="oe_button_box" name="button_box">
<button name="%(estate.estate_properties_offers_view)d" type="action" class="oe_stat_button" invisible="not offer_count">

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

but why do we want to make it invisible if there are no offers? The user might use this button to navigate to the offers view and create an offer from there right away. Please let me know what you think

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

instructed by tutorial

Comment thread estate/views/estate_property_views.xml Outdated
Comment thread estate/views/res_user_views.xml Outdated
Comment thread estate/__manifest__.py Outdated
Comment thread estate_account/__manifest__.py
@bepro-odoo
bepro-odoo requested a review from YassinWalid July 27, 2026 14:50
@bepro-odoo
bepro-odoo force-pushed the 19.0-onboarding-bepro branch from 968ff04 to 3768c17 Compare July 28, 2026 14:48
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.

4 participants