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

Coffee unit #33

Merged
merged 22 commits into from
Oct 15, 2024
Merged

Coffee unit #33

merged 22 commits into from
Oct 15, 2024

Conversation

sepandhaghighi
Copy link
Owner

Reference Issues/PRs

#13

What does this implement/fix? Explain your changes.

  • show_coffee_units_list function added
    --coffee-unit argument added
  • README.md updated

Any other comments?

@sepandhaghighi sepandhaghighi self-assigned this Oct 14, 2024
Copy link

codecov bot commented Oct 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c255c37) to head (444b4eb).
Report is 1 commits behind head on dev.

Additional details and impacted files
@@            Coverage Diff            @@
##               dev       #33   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           80        88    +8     
  Branches        16        18    +2     
=========================================
+ Hits            80        88    +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@sepandhaghighi sepandhaghighi added the enhancement New feature or request label Oct 14, 2024
@sepandhaghighi sepandhaghighi added this to the mycoffee v0.6 milestone Oct 14, 2024
@sepandhaghighi sepandhaghighi marked this pull request as ready for review October 14, 2024 15:11
Copy link
Collaborator

@sadrasabouri sadrasabouri left a comment

Choose a reason for hiding this comment

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

Minor changes I commented.
Do you think we can change this parameter to unit instead of making it specific to coffee?
I'd guess you want to implement some similar thing for water too. Having two parameter to control coffee and water seems over-engineering to me.

"oz": {"name": "ounce", "rate": 0.03527396195},
"lb": {"name": "pound", "rate": 0.00220462262185},
"mg": {"name": "milligram", "rate": 1000},
"kg": {"name": "kilogram", "rate": 0.001}}
Copy link
Collaborator

Choose a reason for hiding this comment

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

"kg": {"name": "kilogram", "rate": 0.001},
}

Copy link
Owner Author

Choose a reason for hiding this comment

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

fixed in 444b4eb

@sepandhaghighi
Copy link
Owner Author

Minor changes I commented. Do you think we can change this parameter to unit instead of making it specific to coffee? I'd guess you want to implement some similar thing for water too. Having two parameter to control coffee and water seems over-engineering to me.

At first, I had planned to add a single argument for the unit, but some of the units are specific to coffee or water—for example, " Approximate number of beans"—so we should add them separately.

@sadrasabouri sadrasabouri merged commit ebf2f97 into dev Oct 15, 2024
46 checks passed
@sadrasabouri sadrasabouri deleted the coffee_unit branch October 15, 2024 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants