[ADD] estate: add initial module structure#1366
Conversation
|
|
|
I see you have a lot of files leftover from when you were using PyCharm, let's try to remove them! |
2ebe8ce to
41367ac
Compare
1bad78c to
1f717c8
Compare
|
Enjoy |
1f717c8 to
caea9be
Compare
caea9be to
a60801f
Compare
bd3002b to
af1db63
Compare
5b95430 to
7055963
Compare
de3504a to
b098b9e
Compare
0d35e8e to
a2837a2
Compare
e3bfc94 to
9e60d69
Compare
09fb758 to
ab1e0d4
Compare
SaddemAmine
left a comment
SaddemAmine
left a comment
There was a problem hiding this comment.
Very good stuff, thank you for the PR Tony!
I see that in older commits, the ci/style issues pop up again, usually you would need to make sure every commit passes CI on its own. For the purposes of this tutorial, I'll leave that up to you to decide if you want to go back and fix the styling errors.
| @@ -0,0 +1,21 @@ | |||
| <?xml version="1.0" encoding="UTF-8"?> | |||
| <odoo> | |||
|
|
|||
There was a problem hiding this comment.
No need for the extra lines here and at L20 btw!
| name="Property Tags" | ||
| parent="estate_menu_settings" | ||
| action="estate_property_tag_action"/> | ||
|
|
There was a problem hiding this comment.
Nitpicking but this is an unnecessary line break
There was a problem hiding this comment.
Same in this file about the line breaks. Again, mostly my style of coding and not a blocking thing per se
| @@ -0,0 +1,75 @@ | |||
| <?xml version="1.0" encoding="UTF-8"?> | |||
| <odoo> | |||
| <!-- 1. Action --> | |||
There was a problem hiding this comment.
| <!-- 1. Action --> | |
| <!-- 1. Actions --> |
| { | ||
| 'name': 'Real Estate', | ||
| 'version': '1.0', | ||
| 'author': 'tomic', |
| "partner_id": record.buyer_id.id, | ||
| "move_type": "out_invoice", | ||
| "invoice_line_ids": [ | ||
| Command.create({ | ||
| "name": f"Commission (6%) - {record.name}", | ||
| "quantity": 1, | ||
| "price_unit": 0.06 * record.selling_price, | ||
| }), | ||
| Command.create({ | ||
| "name": "Administrative fees", | ||
| "quantity": 1, | ||
| "price_unit": 100.00, | ||
| }), | ||
| ], |
There was a problem hiding this comment.
Btw a nice convention we started adopting in my team recently in using single quotes for technical strings and double quotes for the user facing ones. Feel free to start doing that too if it speaks to you. The idea is to be able to tell at a glance if a string is meant to be visible by the user.
| "move_type": "out_invoice", | ||
| "invoice_line_ids": [ | ||
| Command.create({ | ||
| "name": f"Commission (6%) - {record.name}", |
| "price_unit": 0.06 * record.selling_price, | ||
| }), | ||
| Command.create({ | ||
| "name": "Administrative fees", |
| }) | ||
|
|
||
| if invoices_vals: | ||
| self.env["account.move"].with_context(default_move_type="out_invoice").create(invoices_vals) |
There was a problem hiding this comment.
Why are we using default_move_type here?
3 participants
No description provided.