You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PMS, REMS and other vertical modules need the concept of property.
In that goal we choose to make a new base_property with common fields that could be shared with other vertical modules (starting with pms_base and real_estate)
BTW , why not res_property ? to be aligned with odoo's res_*...
The text was updated successfully, but these errors were encountered:
Usually res is not used in module names. We use base_something or directly the name. The module may be called simply property if you want.
base_property is fine for me because we say in the name that this module is a base for something else...
About the model, can it be res.property then ?
There is the module multi_pms_properties, which is designed to add certain common features to property management and could serve as a good foundation for a common properties module across repositories. There is no problem in renaming it to base_property, although since the concept of "property" is widely used in the code for generic purposes, we thought it was more appropriate to introduce the pms prefix to avoid confusion.
PMS, REMS and other vertical modules need the concept of property.
In that goal we choose to make a new base_property with common fields that could be shared with other vertical modules (starting with pms_base and real_estate)
BTW , why not res_property ? to be aligned with odoo's res_*...
The text was updated successfully, but these errors were encountered: