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

CV2-2357: New UX for update to ToS #1818

Merged
merged 8 commits into from
Mar 7, 2024
Merged

Conversation

melsawy
Copy link
Contributor

@melsawy melsawy commented Mar 4, 2024

Description

Send an email to all Check users notifying them that the ToS have been updated.

References: CV2-2357

How has this been tested?

Implemented automated tests.

Things to pay attention to during code review

Please describe parts of the change that require extra attention during code review, for example:

  • File FFFF, line LL: This refactoring does this and this. Is it consistent with how it’s implemented elsewhere?
  • Etc.

Checklist

  • I have performed a self-review of my own code
  • I have added unit and feature tests, if the PR implements a new feature or otherwise would benefit from additional testing
  • I have added regression tests, if the PR fixes a bug
  • I have added logging, exception reporting, and custom tracing with any additional information required for debugging
  • I considered secure coding practices when writing this code. Any security concerns are noted above.
  • I have commented my code in hard-to-understand areas, if any
  • I have made needed changes to the README
  • My changes generate no new warnings
  • If I added a third party module, I included a rationale for doing so and followed our current guidelines

@@ -0,0 +1,12 @@
class UpdatedTermsMailer < ApplicationMailer
layout nil
Copy link

Choose a reason for hiding this comment

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

Use 2 (not 1) spaces for indentation.

@@ -0,0 +1,12 @@
class UpdatedTermsMailer < ApplicationMailer
layout nil
Copy link

Choose a reason for hiding this comment

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

Tab detected.

@melsawy melsawy changed the title CV2-2357: add mail worker and template CV2-2357: New UX for update to ToS Mar 5, 2024
@melsawy melsawy marked this pull request as ready for review March 5, 2024 16:36
@melsawy melsawy requested review from caiosba and DGaffney as code owners March 5, 2024 16:36
Copy link
Contributor

@caiosba caiosba left a comment

Choose a reason for hiding this comment

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

Thanks Sawy, I just had one question.


def notify(recipient, name)
@name = name
@accept_terms_url = "https://meedan.com/legal/terms-of-service"
Copy link
Contributor

Choose a reason for hiding this comment

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

Question: Why this is hard-coded instead of reading from the configuration key tos_url (https://github.com/meedan/check-api/blob/develop/config/config.yml.example#L70)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

puts "[#{Time.now}] Done in #{minutes} minutes."
end
end
end
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice!

Copy link

codeclimate bot commented Mar 6, 2024

Code Climate has analyzed commit 1adb946 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 100.0% (0.0% change).

View more on Code Climate.

@melsawy melsawy merged commit d72ae43 into develop Mar 7, 2024
8 checks passed
@melsawy melsawy deleted the CV2-2357-new-ux-for-update-terms branch March 7, 2024 05:16
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.

2 participants