Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you ๐
If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
[ ] ๐ Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
[ ] ๐ Update the file $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.
See this page for some help in taking your first steps!
As noted in #6230, comments and like messages from multiple people on the same research note show up as separate threads in an email inbox. Instead, they should show up in the same thread. In order to achieve this, we have to make sure the titles of the emails match exactly.
In the files subscription_mailer.rb and comment_mailer.rb, there are different methods for each type of event (e.g., when a note is updated, liked, or initially created. To make all the messages show up in the same email thread, we need to make all the subject lines look the same.
subscription_mailer.rbLet's make all the subject lines look like this one, on line 7:
https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L7
First, replace the following three lines with the exact text from line 7 (above):
https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L22-L24
Then, in the notify_tag_added method, paste the exact text from line 7 right below the method header (i.e., right before the line saying @tag = tag):
https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L32-L59
Finally, on this line:
https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/subscription_mailer.rb#L57
Replace "#{node.title} (##{node.id})" with subject.
comment_mailer.rbChange line 11 of the file:
https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/comment_mailer.rb#L11
to match line 18:
https://github.com/publiclab/plots2/blob/7e2ebf018d021f6f31d5a9d99d242eb5048ba2ba/app/mailers/comment_mailer.rb#L18
[ ] ๐พ Commit your changes
[ ] ๐ Start a Pull Request. There are two ways how you can start a pull request:
If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
You can also edit files directly in your browser and open a pull request from there.
๐ฌโฐ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!
If this happens to you, don't sweat it! Grab another open issue.
๐- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.
๐ฅ- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!
Leave a comment below!
@publiclab/reviewers As for the changes requested in #6230 for comment_mailer.rb, I'm not sure if we want the two statements to use comment.node or comment.parent, so I haven't added them to this FTO yet.
Match each other, and making this one:
and this one:
also identical... that is, the email subjects should all be the same for this set of emails!
Which of these two statements would we like to use, what's the difference, and should those changes be part of the same issue or a separate one?
hey @anthony-zhou, thanks for opening this.
.parent will check if there is an answer associated with the comment then return the node that belongs to the answer, if not, just return the node(which ideally should be the same node as calling .node.....I believe the two methods returns the same node furthermore answers model might be deprecated soon so we can just call .node..makes sense? Thanks
I AM CLAIMING THIS ISSUE @anthony-zhou
@cesswairimu Thanks for the info. I updated the issue with your answer. @developer22-university Please see the updated issue for one additional change to make in comment_mailer.rb. Thanks!
I can claim the issue if still open @anthony-zhou
Sure
On Fri, 31 Jan 2020, 4:19 am Shubhangi Prasad, notifications@github.com
wrote:
I can claim the issue if still open @anthony-zhou
https://github.com/anthony-zhouโ
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/7194?email_source=notifications&email_token=AFAAEQ3US7PENXWOBIKHPY3RANKQVA5CNFSM4KFOABK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKM3LNY#issuecomment-580498871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAAEQZODHH23ZYCLQ7HKFTRANKQVANCNFSM4KFOABKQ
.
@anthony-zhou can I work on this issue?
@anshalshukla Go for it. Best of luck!
hello @anthony-zhou can I work on this issue? thanks !
@rimow Please look for another issue I'll be making a pull request soon.
Hi all! This is still available for anyone to claim. @anshalshukla got pretty far in https://github.com/publiclab/plots2/pull/7944#issuecomment-655004146 -- still needs a bit of work though! Thanks!
Please review it. Thank you for your time.
Most helpful comment
I AM CLAIMING THIS ISSUE @anthony-zhou