Skip to content
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

V18.0 training hyhe #239

Open
wants to merge 36 commits into
base: 18.0
Choose a base branch
from
Open

V18.0 training hyhe #239

wants to merge 36 commits into from

Conversation

hyhevic
Copy link

@hyhevic hyhevic commented Jan 22, 2025

No description provided.

Created house model with the required attributes
permits the base group user for all CRUD operations on the house model
created action with list,kanban and form view and linked it to the menus of the properties in the app
added license in the manifest file to pass the warnings in the ci/cd checks
@robodoo
Copy link

robodoo commented Jan 22, 2025

Pull request status dashboard

added the default values for some fields and non copy constraints
- Added list view with some attributes in the view
- Added the form view as proposed in the ui draft
- Added Available filter to the house model in the search view and group by postcode
- Added salesperson and buyer of the house model as Many2one relationship in house model
- Added these information in new tab in the form view of the house
- created the house tag model
- added the access rights permissions to the base user group
- added a settings menu enacspulating house type and tags
- added the tags in the list and form view of the house model
- Created the offer model
- Added menu, action and list/form view for the offer model
- Added a list view in the notebook pages of the house model page
@nesma-neha
Copy link

This is Odoo module structure:

my_module/
├── __init__.py
├── __manifest__.py
├── models/
│   ├── __init__.py
│   ├── my_model.py
├── views/
│   ├── my_model_views.xml
│   ├── templates.xml
├── security/
│   ├── ir.model.access.csv
│   ├── security.xml
├── data/
│   ├── my_data.xml
│   ├── demo_data.xml

Please follow it 😃

estate/__init__.py Outdated Show resolved Hide resolved
estate/__manifest__.py Outdated Show resolved Hide resolved
estate/data/security/ir.model.access.csv Outdated Show resolved Hide resolved
estate/models/house_tag.py Outdated Show resolved Hide resolved
estate/models/house.py Outdated Show resolved Hide resolved
estate/models/house.py Outdated Show resolved Hide resolved
estate/models/offer.py Outdated Show resolved Hide resolved
estate/models/offer.py Outdated Show resolved Hide resolved
estate/models/offer.py Show resolved Hide resolved
estate/models/house_tag.py Outdated Show resolved Hide resolved
@nesma-neha
Copy link

Also for later; Branch names start with the version number directly
For example: 18.0-training-hyhe

- Added best price attr in the house model as computed attr from the offers' prices
- Added onChange effect on the garden boolean attr
- added the validity attr
- added the deadline attr as computed attr and with inverse changing the validity days of the offer
- added buttons for the property model with their corresponding actions
- changed the buyer of the property to the res.partner table instead of res.user
- added accept/reject offer buttons with their actions
- added checker if the a property has already accepted an offer before (boolean attr in db)
…type

- added check positive constraints on expected/selling_price on the house model
- added UNIQUE constraints in the house_tag/house_type models
- added check positive price constrain in the house offer model
- added some behaviors on the buttons visibility
- added stats button of the number of offers per house_type
- added some color codes to the rows of specific features (sold house, ..)
- added the validation of not deleting house if the state is neither new nor cancelled
- added an automation on the creation of offer to change the state of the property to 'Offer Received' and validation of only adding offers ith prices greater than all that existed before
- added the users model with extra field of the properties they are selling
- added the page of the notebook to the res.users base view as inherited view
- created estate_account module app for handling the invoices when a property is sold
- added the property model inherited from the house with the overriding of the sell method to create invoices on selling
- refactored the names of some models to follow the naming convention
- changed the respective references of these models in the xml, py and csv files
… some attr

- refactored names of the model classes to PascalCase
- refactored names of attributes of the relationships to be singular_ids
- refactored the db values of the selection fields to be snake case
- changed the record in the kanban view to use the raw_value of the state instead of the value so we compare to the db value in the conditions
- removed the menu linked to the house.offer action because the action has a domain based on the active_id and the menu is not setting active_id in the context
…training

- seperated the counter in a sub component to be used in the playground
- added a card component and refactored the folder structure
- added a card component with props{title, content} and added it to the playground template
- refactored the folder structure with adding the components/ directory to have all the components inside
- added the card content in the playground as html
- added validations and description for the props of the card component
- added an age prop with positive validation
- added a non extra space validation in the card title
- added the description of the card props
- added the counters sum function in the playgorund
- added a function that sums all the counters in the playground binded to the playground context
- added the todolist and the todoitems
- changed the style of the todo in case of completion
- added a text muted class and line through on the card of the completed todo
- added a todo creation instead of the hardcoded todos list
- added a function to create a todo and stored them in a useState var
- commented the old uis in the playground template except for the todoslist
- added a custom hook that focuses an input field and used it in the todolist component
- added a toggling todo feature
- added a checkbox on the todoitem template with t-model the state of the todoitem
- fixed the todoitem cards have the id starting from 1 instead of 0 based
- added the delete todo button that deletes a todo
- changed the content of the card to use slots instead
- added a toggler visibility button on the card component
@hyhevic hyhevic force-pushed the v18.0-training-hyhe branch from 4cb75b8 to c1a26ce Compare January 31, 2025 14:09
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