-
Notifications
You must be signed in to change notification settings - Fork 760
Technical Training - Kenneth #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
KennethOfficial
wants to merge
59
commits into
odoo:master
Choose a base branch
from
KennethOfficial:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…model for enhanced property details and features.
… in the manifest data for the estate module.
…ews.xml' to the manifest data for the estate module.
… property form view definition in estate_property_views.xml.
…el name from 'estate_property' to 'estate.property' in estate_property.py for consistency with Odoo naming conventions.
…/estate_menus.xml' to the manifest data for the estate module.
…nd selling_price fields, ensuring proper data handling in the EstateProperty model.
…lt value for date_availability field in EstateProperty model to two months from today.
…tate_property_views.xml to include list view.
… entries for clarity, and add logging to EstateProperty model initialization in estate_property.py.
…, adding detailed logging for debugging during model setup.
…y model and views, streamlining the codebase for improved maintainability.
…tion record in estate_property_views.xml for improved clarity and consistency.
…nition for estate properties and updating the action window to reference the new list view, improving user interface clarity and functionality.
…e module, reflecting the latest changes and improvements.
… form view definition for estate properties in estate_property_views.xml, enhancing the user interface and data entry experience.
…iews.xml, enhancing search functionality and user experience. Update action window to reference the new search view for improved navigation.
…e form view reference from estate_property_views.xml, streamlining the view configuration for improved clarity.
…ferences to view IDs in estate_property_views.xml, simplifying the view configuration for better maintainability.
…ut view definitions in estate_property_views.xml for improved maintainability and clarity.
…rm and search views, enhancing maintainability and clarity in the estate property module.
…l to enhance view configuration and improve user navigation within the estate property module.
…_type_id field to EstateProperty model, and enhance estate_property_views.xml with property type field and filter for improved property management and user experience.
…son_id and buyer_id fields to EstateProperty model, and enhance estate_property_views.xml with a new "People" page for better property management and user experience.
…field to EstateProperty model, and enhance estate_property_views.xml with tag selection for improved property categorization. Also, add access rights for estate_property_tag in ir.model.access.csv and include menu item for property tags in estate_menus.xml.
…s field to EstateProperty model, and enhance estate_property_views.xml with a new "Offers" page for better property management. Also, add access rights for estate_property_offer in ir.model.access.csv.
…nd deadline fields, and add computed methods for best price and total area. Update views to display new fields for improved property offer management.
…nge method for garden in EstateProperty model to manage garden area and orientation dynamically.
…tion methods for accepting and refusing offers in EstatePropertyOffer model, and add action methods for cancelling and selling properties in EstateProperty model. Enhance views to include buttons for these actions, improving property offer management and user experience.
…onstraints for positive offer prices in EstatePropertyOffer, unique property tag names in EstatePropertyTag, unique property type names in EstatePropertyType, and positive expected and selling prices in EstateProperty for improved data integrity.
…SQL constraints in EstatePropertyOffer, EstatePropertyTag, EstatePropertyType, and EstateProperty models to use the new Constraint class for improved data integrity and maintainability.
…statePropertyType, and EstateProperty models to use _sql_constraints for improved data integrity and maintainability.
…ation constraint in EstateProperty model to ensure selling price is not lower than 90% of expected price, enhancing data integrity and user feedback.
… views with a new "Properties" tab for better property management.
…ing to EstatePropertyOffer, EstatePropertyTag, EstatePropertyType, and EstateProperty models for improved data retrieval and organization.
…ing and update the view to include a handle widget for better user experience in property type management.
…eld to EstatePropertyTag model, and enhance tag_ids field in views to utilize color options for improved user experience in property management.
…y offers and tags editable in the list view, and enhance button visibility in property offer and property views based on status for improved user experience in property management.
…ffer statuses and updating the living area field with a filter domain. Also, improve the action window definition by including a context for better search functionality in property management.
…tePropertyType model with offer_ids and offer_count, and update views to include property type in offers and a stat button for offer count. This improves data relationships and user interaction in property management.
…ts and enhancing the tag_ids field with color options for improved user experience in property management.
…on for the stat button from the estate_property_offer_views.xml to the estate_property_type_views.xml, ensuring better structure and accessibility for property offers in the user interface.
…inition for property offers in estate_property_type_views.xml, ensuring improved accessibility and functionality in the user interface. Remove the previous definition from estate_property_offer_views.xml for better organization.
…rarily disable the action for viewing offers, improving the clarity of the form layout while maintaining the existing structure for future use.
…the action button for viewing offers in estate_property_type_views.xml, and add new lines in estate_property_offer.py for code consistency. This enhances the user interface and maintains code readability.
…odels to enforce business rules on offer creation and property deletion. This ensures offers are higher than existing ones and restricts deletion of properties in certain states, enhancing data integrity and user experience.
…sers_views.xml to data list, enhancing module functionality and ensuring proper integration of user views.
…on of offers, ensuring that each offer price is validated against existing offers. This enhances data integrity and maintains the flow of property state updates.
…tion of offers, ensuring each offer price is compared against existing offers. This improves data integrity and user experience in property management.
…nit__.py to import estate_account model, enhancing module structure and security compliance.
…re and support additional functionalities related to property management.
…del, including commission and administrative fee calculations. Add debugging logs for better traceability during property sales.
…ode to include Kanban. Increment version number to 18.0.1.0.5 in __manifest__.py for module enhancement.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.