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

report/log: add lunar start time options 🌔 #215

Merged
merged 2 commits into from
Jul 30, 2018

Conversation

mguentner
Copy link

supplying --luna (e.g. instead of --month), the last full moon
will be taken as the start date of the summary.
The start date of a lunar month is not fixed, some cultures use
the new moon (chinese), some use the full moon (hindu) and some
use the first sight of the crescent (jewish / hebrew).

I implemented the full moon calendar because today is a full moon
and a total lunar eclipse.

My hope is to adjust my work load according the moon cycle.

Peace.

@jmaupetit
Copy link
Contributor

That's a wonderful feature 😉 Can you please fix formatting issues (see travis job output)?

@mguentner
Copy link
Author

All 💚

Copy link
Contributor

@jmaupetit jmaupetit left a comment

Choose a reason for hiding this comment

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

Great job, thank you for this!


aniceday_result = get_last_full_moon(aniceday)

assert aniceday_result == aniceday_lastMoon
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you remove the two empty lines above?

-----|-----
`-f, --from DATE` | Date and time of start of tracked activity [required]
`-t, --to DATE` | Date and time of end of tracked activity [required]
`--help` | Show this message and exit.
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like this should not be part of this PR, but was missing...

@jmaupetit jmaupetit requested a review from k4nar July 30, 2018 07:18
@mguentner
Copy link
Author

@jmaupetit Done. I will squash a last time before you merge.

Copy link
Collaborator

@k4nar k4nar left a comment

Choose a reason for hiding this comment

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

🌕

Maximilian added 2 commits July 30, 2018 16:38
supplying --luna (e.g. instead of --month), the last full moon
will be taken as the start date of the summary.
The start date of a lunar month is not fixed, some cultures use
the new moon (chinese), some use the full moon (hindu) and some
use the first sight of the crescent (jewish / hebrew).

I implemented the full moon calendar because today is a full moon
and a total lunar eclipse.

My hope is to adjust my work load according the moon cycle.

Peace.
@mguentner
Copy link
Author

@jmaupetit @k4nar squashed and still green

@k4nar k4nar merged commit c170cac into jazzband:master Jul 30, 2018
@mguentner mguentner deleted the fullmoon branch July 30, 2018 21:42
jmaupetit added a commit that referenced this pull request Mar 25, 2019
Added:

- New `add` command (#202)
- Add lunar start time options to the `report` and `log` commands (#215)
- Aggregate reports by day (#231)
- Fish shell completion (#239)
- Add support for first day of the week configuration in reports and logs (#240)
- Python 3.7 support (#241)
- Add `start --no-gap` and `stop --at` options (#254)

Changed:

- The `edit` command now checks data consistency (#203)
- Current state saving is now improve when using Watson as a library (#214)
- Prevent calling `get_start_time_for_period` multiple times (#219)

Fixed:

- Improved support for UTF-8 with Python 2 (#211)
- Zsh completion for tags and projects with spaces in their names (#227)
- Typos in commands output (#230, #235)
- Project URL of the project in PyPI (#260)

Removed:

- Python 3.3 support (#210).
@jmaupetit jmaupetit mentioned this pull request Mar 25, 2019
jmaupetit added a commit that referenced this pull request Mar 25, 2019
Added:

- New `add` command (#202)
- Add lunar start time options to the `report` and `log` commands (#215)
- Aggregate reports by day (#231)
- Fish shell completion (#239)
- Add support for first day of the week configuration in reports and logs (#240)
- Python 3.7 support (#241)
- Add `start --no-gap` and `stop --at` options (#254)

Changed:

- The `edit` command now checks data consistency (#203)
- Current state saving is now improve when using Watson as a library (#214)
- Prevent calling `get_start_time_for_period` multiple times (#219)

Fixed:

- Improved support for UTF-8 with Python 2 (#211)
- Zsh completion for tags and projects with spaces in their names (#227)
- Typos in commands output (#230, #235)
- Project URL of the project in PyPI (#260)

Removed:

- Python 3.3 support (#210).
jmaupetit added a commit that referenced this pull request Mar 25, 2019
Added:

- New `add` command (#202)
- Add lunar start time options to the `report` and `log` commands (#215)
- Aggregate reports by day (#231)
- Fish shell completion (#239)
- Add support for first day of the week configuration in reports and logs (#240)
- Python 3.7 support (#241)
- Add `start --no-gap` and `stop --at` options (#254)

Changed:

- The `edit` command now checks data consistency (#203)
- Current state saving is now improve when using Watson as a library (#214)
- Prevent calling `get_start_time_for_period` multiple times (#219)

Fixed:

- Improved support for UTF-8 with Python 2 (#211)
- Zsh completion for tags and projects with spaces in their names (#227)
- Typos in commands output (#230, #235)
- Project URL of the project in PyPI (#260)

Removed:

- Python 3.3 support (#210).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants