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

release: v1.4.9 #2365

Merged
merged 1 commit into from
Sep 4, 2021
Merged

release: v1.4.9 #2365

merged 1 commit into from
Sep 4, 2021

Conversation

iGormilhit
Copy link

Co-Authored-by: Igor Milhit [email protected]

Why are you opening this PR?

  • For the v1.4.9 release.

How to test?

  • Check changed files.

Code review check list

  • Commit message template compliance.
  • Commit message without typos.
  • File names.
  • Functions names.
  • Functions docstrings.
  • Unnecessary commited files?
  • Cypress tests successful?

@iGormilhit iGormilhit self-assigned this Sep 3, 2021
@github-actions github-actions bot added the dev: documentation About changelog, release notes, installation procedures, gh templates... label Sep 3, 2021
@iGormilhit iGormilhit added this to the v1.4.9 milestone Sep 3, 2021
@iGormilhit iGormilhit marked this pull request as ready for review September 3, 2021 16:42
@iGormilhit iGormilhit requested a review from jma September 3, 2021 16:47
This patch brings many improvements and fixes on the notification
process, such as:

- Preventing to send (again and again) notifications that are in an
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Preventing to send (again and again) notifications that are in an
- Preventing to repeatedly send notifications that are in an


- Preventing to send (again and again) notifications that are in an
error state.
- Preventing notification to be in an error state if the pickup
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Preventing notification to be in an error state if the pickup
- Preventing notifications to be in an error state if the pickup

- Preventing notification to be in an error state if the pickup
location is deleted.
- Cancelling generated notifications if the situation changed between
the generation and the processing. In deed, some notifications are
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
the generation and the processing. In deed, some notifications are
the generation and the processing. Indeed, some notifications are

- Cancelling generated notifications if the situation changed between
the generation and the processing. In deed, some notifications are
asynchronous in order to be able to group several notifications of
the same type to the same patron. But in that delay, the notification
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
the same type to the same patron. But in that delay, the notification
the same type to the same patron. But in the meantime, a notification

- Preventing to send reminders if the library is closed between the due
date and the notification processing (`#2303`_).
- Computing the date at which the due soon notification has to be sent when
creating the loan, instead of through a recurring task, in order to
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
creating the loan, instead of through a recurring task, in order to
creating the loan, instead of through a recurring task, in order to improve

date and the notification processing (`#2303`_).
- Computing the date at which the due soon notification has to be sent when
creating the loan, instead of through a recurring task, in order to
performance and get a more stable date.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
performance and get a more stable date.
performance and apply a more stable date.

- Computing the date at which the due soon notification has to be sent when
creating the loan, instead of through a recurring task, in order to
performance and get a more stable date.
- Processing the due soon and overdue notification as soon as possible, to
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Processing the due soon and overdue notification as soon as possible, to
- Processing due soon and overdue notifications as soon as possible, to

Comment on lines 24 to 25
This patch brings many improvements and fixes on the notification
process, such as:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This patch brings many improvements and fixes on the notification
process, such as:
This patch brings several improvements and fixes on the notification
process:

Co-Authored-by: Igor Milhit <[email protected]>
@iGormilhit iGormilhit merged commit 92bd6b7 into rero:dev Sep 4, 2021
@iGormilhit iGormilhit deleted the release-v1.4.9 branch October 13, 2021 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev: documentation About changelog, release notes, installation procedures, gh templates...
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants