Git First Timers

There are lots of people that need help and want to make our community of software development open and inclusive.

This list displays the top 100 Open Issues with the 'first-timers-only' tag on Github.com.

That means this is a curated list of some of the best, most open, open source projects on the internet!

1 Review documentation of Throubleshooting page

Find it on GitHub

todo Read and spellcheck the page: https://github.com/arduosoft/RawCMS/blob/master/docs/Thoubleshooting.md

Any suggestions on contents are welcome.

steps 1. fork the project 2. make the changes 3. create a PR

2 Change the log path

Find it on GitHub

in file https://github.com/arduosoft/RawCMS/blob/master/RawCMS/conf/NLog.Development.config there is a wron path.

The configuration uses NLog settings.

What is expected The log are written on the main repo folder, at root level. The log folder will be "log". No changes are required on all other log files. The folder must be created if not present( createDir attribute on settings). The folder is marked as ignored on .gitignore ```xml

``` https://github.com/nlog/NLog/wiki/File-target

Steps 1. Fork the project 2. Start a new branch from develop 3: Implement changes 4. Make a pull request to the original development branch

** key points ** - change the log - the log must be written on log folder inside the main repo folder - log folder must be ignored in git

3 Change t to translation in _events.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 _events.html.erb 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! Changes to be made ![Screenshot 2020-02-19 at 1 36 38 PM](https://user-images.githubusercontent.com/57896905/75097949-a0f51500-55d6-11ea-81af-43cd76e6bc20.png) Do it for line 4, 12, 14

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

4 Change t to translation in _dashboard.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 _dashboard.html.erb 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! Changes to be made ![Screenshot 2020-02-19 at 1 36 38 PM](https://user-images.githubusercontent.com/57896905/75097927-4d82c700-55d6-11ea-8723-ae1d267bd95c.png) Do it for line 3, 10, 11, 12, 13, 15, 40

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

5 Add more information to Products

Find it on GitHub

Add more information to Products model i.e. title, description

Check out what data other eCommerce sites hold. but keep it simple.

6 Not showing correctly on first load

Find it on GitHub

@mresmaeili I've seen your issue

Can you check if this version has the same problem? I don't understand where's the problem, the link you attached there is fine for me.

7 Shape from particle.js

Find it on GitHub

Referencing this issue from the old project. It's interesting but I need to understand it first.

@SoulDesignerTom if you can explain with more details I try to work on it

8 Change t to translation in _related.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 _related.html.erb 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! Changes to be made ![Screenshot 2020-02-19 at 1 36 38 PM](https://user-images.githubusercontent.com/57896905/74814589-9eb46180-531d-11ea-979c-d79b5a1a900f.png) Do it for line 19, 38, 42

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

9 Change t to translation in _new_question.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 newquestion.html.erb 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!

Changes to be made ![Screenshot 2020-02-19 at 1 36 38 PM](https://user-images.githubusercontent.com/57896905/74814353-159d2a80-531d-11ea-9fa3-6065ac80b83c.png) Make above changes on line 24, 25, 26, 28

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

10 Change the function t to translations in app/views/wiki/index.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Link to file

The function t( ) needs to be changed in the respective lines:

5. <%= raw t('wiki.index.wikipagestaggedwith', :tag => params[:id]) %>
9. <%= raw t('wiki.index.wikipagesby', :url1 => "/people/"+@user.name, :user => @user.name, :notelength => @user.notes.length, :time => 
14. <%= t('wiki.index.collaborativedocumentation') %>
16. <%= t('wiki.index.aboutcollaboration') %> <%= raw t('wiki.index.aboutwikipages') %>
22. <%= t('wiki.index.createwikipage') %>
changes should be something like this in all above respective lines mentioned.
5. <%= raw translation('wiki.index.wikipagestagged_with', :tag => params[:id]) %>

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

11 Parallax

Find it on GitHub

The parallax was in development when I forked the source repo, in fact it has some issues keeping the particles aligned.

12 Showing number of results found in email search

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 useremail.html.erb 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!

Do the below shown change ![Screenshot 2020-02-15 at 11 37 39 PM](https://user-images.githubusercontent.com/57896905/74592936-367b2c80-504c-11ea-953e-5c93eaecb703.png)

Expected Behaviour ![Screenshot 2020-02-15 at 11 36 31 PM](https://user-images.githubusercontent.com/57896905/74592916-0469ca80-504c-11ea-9baa-7a3f2e2c6d49.png)

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

13 Add Images to Products

Find it on GitHub

  • Let users upload image
  • This is primarily for learning. We encourage first timers. Please join our discord to have a chat!

14 Add Point of Sales section

Find it on GitHub

  • Integrates with products
  • This is primarily for learning. We encourage first timers. Please join our discord to have a chat!

15 Add Accounting Section

Find it on GitHub

  • Feel free to do some research
  • This is primarily for learning. We encourage first timers. Please join our discord to have a chat!

16 Add Payroll Section

Find it on GitHub

  • Requires Employee model
  • This is primarily for learning. We encourage first timers. Please join our discord to have a chat!

17 Change function t to translation in app/views/notes/index.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 index.html.erb 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!

Change t to translation as shown below ![Screenshot 2020-02-14 at 4 39 21 PM](https://user-images.githubusercontent.com/57896905/74526067-9688aa80-4f48-11ea-845e-df118a797f7d.png) Do it for line 3(2 t are there), 8 , 10, 12, 14(2 ts) ,16, 25 ,28 , 31

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

18 change function t to translation in app/views/notes/_responses.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 _responses.html.erb 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!

Change t to translation as shown below ![Screenshot 2020-02-14 at 4 30 37 PM](https://user-images.githubusercontent.com/57896905/74525670-a9e74600-4f47-11ea-929e-feea92cc6f48.png) Do it for line 16, 35, 40, 47

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

19 change function t to translation in app/views/wiki/_header.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [x] πŸ™‹ 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!

  • [x] πŸ“ 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!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff Line 22 - <%= raw t('wiki.show.revision_from', :time => @revision.created_at.to_s(:long)) %> + <%= raw translation('wiki.show.revision_from', :time => @revision.created_at.to_s(:long)) %> Line 24 - <%= t('wiki.show.view_all_revisions') %> + <%= t('wiki.show.view_all_revisions') %>

  • [x] πŸ’Ύ Commit your changes

  • [x] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [x] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

20 <br> tag in useremail

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Add a
tag in line 18
![Screenshot 2020-02-14 at 12 58 51 AM](https://user-images.githubusercontent.com/57896905/74470824-38ff4a00-4ec5-11ea-8153-09a5fd0e41dc.png) Expected Behaviour ![Screenshot 2020-02-14 at 1 03 26 AM](https://user-images.githubusercontent.com/57896905/74471239-e6725d80-4ec5-11ea-9b55-790285efecbf.png)

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

21 Change the function t to translation in notes/_responses.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 notes/_responses.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

There are 4 instances of t(..) in this file that need to be changed to translation(..)

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

22 Change the function t to translation in app/views/sidebar/_list.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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.

Link to file

See this page for some help in taking your first steps! The function needs to be changes in the following lines:

7. <%= raw t('sidebar.list.mailinglist', :mailinglist => mailinglist, :url1 
12. <%= t('sidebar.list.subscribe') %>
26. <%= t('sidebar.list.all_topics') %>

The changes should look like this in respective lines:

7. <%= raw translation('sidebar.list.mailinglist', :mailinglist => mailinglist, :url1 

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

23 Implement polygon mask

Find it on GitHub

I've seen the polygon mask on this repository (it's a fork) and I loved it. I wanted to implement it in this repo too.

24 change function t to translation in app/views/wiki/edit.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [x] πŸ™‹ 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!

  • [x] πŸ“ 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!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

```diff -

<%= t('wiki.edit.didyoumean') %>:

+

<%= translation('wiki.edit.didyoumean') %>:

- <%= raw t('wiki.edit.whatsawikipage') %> + <%= raw translation('wiki.edit.whatsawikipage') %> -

<%= t('wiki.edit.editingpage') %>: <%= @node.latest.title %>

+

<%= translation('wiki.edit.editingpage') %>: <%= @node.latest.title %>

-

<%= t('wiki.edit.createpage') %>: <%=h params[:id] %>

+

<%= translation('wiki.edit.createpage') %>: <%=h params[:id] %>

-

<%= raw t('wiki.edit.agreetoopensourcework', :url1 => "/licenses") %>

+

<%= raw translation('wiki.edit.agreetoopensourcework', :url1 => "/licenses") %>

```

  • [x] πŸ’Ύ Commit your changes

  • [x] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [x] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

25 .its command with compound properties failing TypeScript check

Find it on GitHub

Cypress v3, v4

Our typescript definition for cy.its command "understands" the properties of the subject, thus it can do

js cy.wrap({ foo: 1 }).its('foo') // yup, subject has property "foo"

but it does not understand nested (compound) properties that Lodash _.get can do and we use under the hood

js cy.wrap({ foo: { bar: 1 } }).its('foo.bar') // oops, TypeScript freaks out, "foo.bar" is invalid

Maybe someone can look at Lodash and its TypeScript definition for _.get to see if they have solved this problem and bring the solution?

26 Add Unit Tests

Find it on GitHub

27 change function t to translation in app/views/wiki/index.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [x] πŸ™‹ 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!

  • [x] πŸ“ 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!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff - <p><%= t('wiki.index.about_collaboration') %> <%= raw t('wiki.index.about_wiki_pages') %></p> + <p><%= translation('wiki.index.about_collaboration') %> <%= raw t('wiki.index.about_wiki_pages') %></p>

  • [x] πŸ’Ύ Commit your changes

  • [x] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [x] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

28 Add tests

Find it on GitHub

Add intergration tests

29 Add permission levels

Find it on GitHub

Currently we have only login, not permission control. A basic classification would be admin and non-admin accounts.

30 Link from tab_handling_anchor_links_spec.js to stubbing-spying__window

Find it on GitHub

1) Please create a linkage between tabhandlinganchorlinksspec.js and stubbing-spying__window. Both are tackeling the same problem.

2) Please explain what method is the better approach (if generally possible) or give some hints why/when this or that should be used.

Thank you

31 Change the function t to translations in app/views/notes/tools_places.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Link to file

The changes should look like this in the respective lines:

28. <%= translation('notes.tools_places.tools') %>

  1. <%= translation('notes.tools_places.places') %>
  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

32 TEST Lamdas Functionality

Find it on GitHub

Test and improve Lambdas functionality (Lambdas are created for work with external system) ![2020-02-08 085611-Raw CMS GUI](https://user-images.githubusercontent.com/17206853/74081590-f9fa7000-4a50-11ea-965c-87d35186d3ba.png)

  • [ ] Write lambda for reads data from an external system

  • [ ] Write lambda for call internal API and save your external data

  • [ ] Improve documentation with examples

Any improvement suggestions extending this functionality is well accepted.

33 GraphQL Test Acceptance

Find it on GitHub

Verify that all GraphQL functionality works fine:

  • [ ] Query: Read data from mapped schema using all data type:

    • Integer
    • Number
    • Boolean
    • Text
    • DateTime
    • Related Object
  • [ ] Filters: Apply query filter

    • Filter single field
    • Filter multiple field
    • Filter using RawQuery
  • [ ] Paging: Try paging functionality

34 {log:false} of clearLocalStorage doesn't work.

Find it on GitHub

Current behavior:

cy.clearLocalStorage({log:false}) should not show the command on the reporter. But it does.

Desired behavior:

It should not show the command.

Test code to reproduce

js it('test', () => { cy.clearLocalStorage({log:false}) })

Result:

![Screenshot from 2020-02-06 15-42-33](https://user-images.githubusercontent.com/8130013/73912310-87c24800-48f7-11ea-98ad-9b7f1e562578.png)

Versions

3.8.3

35 Make the position argument type of click, dblclick, rightclick more specific

Find it on GitHub

Current behavior:

Currently, the type of position in click, dblclick, rightclick is just string. Because of this, we cannot get the help of Intellisense.

Desired behavior:

They should be replaced to PositionType like scrollTo, etc.

Test code to reproduce

js it('test', () => { cy.get('#button').click('top')`. }

Intellisense doesn't work.

![Screenshot from 2020-02-06 15-41-09](https://user-images.githubusercontent.com/8130013/73912442-db349600-48f7-11ea-9c1d-46c2e555ece8.png)

Versions

3.8.3

36 Hello World Tutorial "Xcode is not installed." error

Find it on GitHub

Hi,

Following the Hello World tutorial I got the error "Xcode is not installed." when trying to build the iOS version of the Hello World App. The problem turned out to be that Xcode does not by default install the command line tools and you have to go to Preferences -> Locations -> Command Line Tools and select the tools (in my case "Xcode 11.3.1").

Probably an idea to add this to the tutorial.

Keep up the good work,

-- Howard.

37 Change colors of X and O that complements each other

Find it on GitHub

This is an issue to all the first-timers-only out there

38 Need IDs for headings so that we can link anchor tags

Find it on GitHub

For example, I want to show "cy.check()" examples by sending an URL. But there is no URL to send - only the top-level page https://example.cypress.io/commands/actions.

39 Change function from t to translation in app/views/notes/_tagged_notes.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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.

File link:"https://github.com/publiclab/plots2/blob/master/app/views/notes/taggednotes.html.erb" See this page for some help in taking your first steps!

Below it shows the lines in which the function t needs to be changed to translation.

9.  <%= raw t('notes.taggednotes.byauthortimeago',
11. <%= t('notes.taggednotes.views') %>
16. <%= t('notes.taggednotes.readmore') %>
23. <%= t('notes.taggednotes.spam') %>
The changes should look like this similarly need to change rest.
11. <%= translation('notes.taggednotes.views') %>
- [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:
  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

40 Create a toggle to close/open all folders in Tests list

Find it on GitHub

Current Behavior: Currently there seems to be no way to have all your folders defaulted to close when you open up Cypress.

The results is a messy UI that isn't as clean when you try and organize your many Cypress tests into folders.

Desired Behavior: Have a setting option to default your folders to close on Cypress open that way you can navigate a cleaner interface when you organize your multiple tests into their appropriate folders.

![Screen Shot 2020-01-30 at 4 46 20 PM](https://user-images.githubusercontent.com/6404079/73503230-8dacac00-4380-11ea-9a1c-f5da020361ef.png)

41 List of integration specs gives no indication it can be or is collapsed

Find it on GitHub

Cypress 3.8.3

You can click on "Integration tests" heading

which closes the file tree - and you have no idea that it was collapsed and can be opened. Surprised me once when I did not see any specs and was like ... where are they?!

Need some kind of icon next to it.

42 The tests list hierarchy is confusing in the Desktop-GUI

Find it on GitHub

I find the tree view in the test-runner to be rather confusing because it looks like folders are on a separate level than files.

Current behavior:

As seen in the screenshot below, it looks like feature is on the same level as 1, 2, etc., but it's actually their parent. And it looks like 3 is on a level below 2, but it's actually its sibling. It becomes even more messy with several levels and folders opened (which they all are by default).

![image](https://user-images.githubusercontent.com/142162/73465411-a4530300-4380-11ea-8af7-711f3a26398a.png)

Desired behavior:

Please remove the unnecessary arrow (open/closed state is already shown with the open/closed folder icon), and have the folder icon line up with the file icons, like this:

![image](https://user-images.githubusercontent.com/142162/73465855-496ddb80-4381-11ea-84ac-49fad5a7af8d.png)

Versions

Cypress: 3.8.3

43 Refactor code to eventually remove jquery dependency - part 1

Find it on GitHub

First Time?

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

Problem

What happens:

JQuery is the 2nd biggest resource we are pulling in (first is Leaflet.js), slowing down page loading time and we barely even use it.

Solution

Let's start refactoring any jQuery find in the code base to vanilla JS. In this issue, we will tackle the below code. Please refactor the ajax implementation to use XHR instead.

https://github.com/publiclab/Leaflet.DistortableImage/blob/e0b51303151565dda66e075653c328f488acf169/src/edit/DistortableCollection.Edit.js#L260-L346

Step by Step

  • [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
  • [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
    • [ ] Create a new feature branch with a unique name descriptive to the issue
  • [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
  • [ ] Reference this issue in your pull request body
  • [ ] Once you submit your pull request, if there's an additional checklist provided for getting it merged, get those boxes checked off. Either way, mention me @sashadev-sky for a review.

πŸ’¬ Get help

If you need any help - here are some options:

  • Comment below
  • Join our gitter chat at https://gitter.im/publiclab/publiclab

44 Change the function t to translations in app/views/notes/_draft_notes.html.erb

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Naviagte to file: app/views/notes/draftnotes.html.erb

The function t in lines 12,13,14,16,27,30,45,46,50 needs to be changed to translation The changes should look like:

diff 12. <%= translation('notes._notes.moderate_first_time_post') %> <br class="d-none d-lg-inline"/> 13. <%= translation('notes._notes.approve') 14. <%= translation('notes._notes.spam') 16 <%= raw translation('notes._notes.pending_approval', :url1 => '/wiki/moderation') %> Similarly rest of the lines needs to be changed.

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

45 Fix layer control not loaded on map page

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 map.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Problem

Layer and embed control are not added to the map in https://stable.publiclab.org/map#3/1.5818302639606454/0 because of a reference error

Solution

Change this line here: https://github.com/publiclab/plots2/blob/aa3b8644e365080e264e73590529ff03bb63cb08/app/views/map/map.html.erb#L105

to 'Gray-scale': baseLayer

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

46 Misleading cy.task error message when returning Promise<undefined>

Find it on GitHub

Current behavior:

When running a task returning promise that fulfils with undefined, we get an error with following message: The task 'exampleAsyncTask' returned undefined. You must return a promise, a value, or null to indicate that the task was handled.

Desired behavior:

Cypress should either handle promises fulfilling to undefined, or give clear error message that it's not allowed (i.e.The task 'exampleAsyncTask' returned promise fulfilling with undefined.).

Test code to reproduce

  1. Clone https://github.com/cypress-io/cypress-test-tiny
  2. Create simple task that returns promise resolving with undefined javascript // plugins/index.js module.exports = (on, config) => { on("task", { exmapleAsyncTask() { return new Promise(resolve => setTimeout(resolve, 100)); } }); };
  3. Execute the task in test javascript describe("page", () => { it("works", () => { cy.visit("https://example.cypress.io"); cy.task("exmapleAsyncTask"); }); });

Test fails with: ``` CypressError: cy.task('exmapleAsyncTask') failed with the following error:

The task 'exmapleAsyncTask' returned undefined. You must return a promise, a value, or null to indicate that the task was handled. ```

Changing task promise to return any value fixes the issue: javascript exmapleAsyncTask() { return new Promise(resolve => setTimeout(() => resolve(42), 100)); }

Versions

Cypress 3.8.2 macOS 10.14.6

47 Add Call-To-Action button to landing page

Find it on GitHub

  • [ ] Bug
  • [ ] Clean up
  • [ ] Question
  • [x] Enhancement
  • [ ] Suggestion
  • [ ] Other

What needs to be done.

Include a new simple button under the header that will route to the playground.

Why

Something simple for the user to quickly get started with their coding.

How

Use react-router and the material Ui button component that routes to the playground. Make the button pop and stand-out.

48 Ctrl+F to set focus on the search bar

Find it on GitHub

Current behavior:

Pressing Ctrl+F does nothing at the moment as this keybinding seems not be bound to anything.

Desired behavior:

I want said keybinding to set focus on the search bar in the GUI (and select all existing text), since I'm using the search bar quite often to find files.

Test code to reproduce

N/A

Versions

3.8.2 and older

49 Format the json file properly so that each movie will have all details in a proper way

Find it on GitHub

3 ## the json file properly so that each movie will have all details in a proper way.

The JSON apparently needs to formatted using movie names as keys ; hence the actual CSV format needs to be preserved. https://github.com/opencodeiiita/MontyPythonClass/pull/47#issuecomment-576268214

50 Cypress screenshot and video size are restricted to 800 x 600 in Chrome Headless

Find it on GitHub

Current behavior:

When running cy.screenshot(), the screenshot differs when running in Chrome Headless vs Chrome Headed vs Electron Headless:

Electron Headless: ![test1](https://user-images.githubusercontent.com/57146040/72824347-19b52a00-3c43-11ea-8e77-94df59cff06d.png)

Chrome Headed: ![test1](https://user-images.githubusercontent.com/57146040/72824402-2e91bd80-3c43-11ea-92ef-43a4580f98a0.png)

Chrome Headless: ![test1](https://user-images.githubusercontent.com/57146040/72824243-f68a7a80-3c42-11ea-979e-96d25709f221.png)

Desired behavior:

It seems as though any screenshot taken while running headless chrome will produce an image that is only 800x600 pixels. This is an issue because i would like to run all tests using headless chrome, however the screenshots headless chrome produces are not large (wide/tall) enough to fully capture my application.

When running chrome headless, changing the size using cy.viewport only works when the given size is less than 800x600. For example if i call cy.viewport(1920,1080) then call cy.screenshot(), the screenshot will be 800x600. However if i call cy.viewport(700,500) then call cy.screenshot(), the screenshot will be 700x500.

Test code to reproduce

```js cy.visit('https://google.com/')

cy.screenshot('test1') //produces a 800x600 pixel image

cy.viewport(700,500) cy.screenshot('test2') //produces a 700x500 pixel image

cy.viewport(1920,1080) cy.screenshot('test3') //produces a 800x600 pixel image ``` <!-- If we cannot fully run the tests as provided the issue WILL BE CLOSED --> <!-- Issues without a reproducible example WILL BE CLOSED -->

Versions

Cypress 3.8.2 Windows 10 Resolution 1920x1200 node 12.13.1 npm 6.12.1 <!-- Cypress, operating system, browser -->

51 Colobar default image is not correct.

Find it on GitHub

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!

You will have to fix a module name colorbar. The issue is that the starting of the colorbar overlay is shifted a bit right. Refer the below GIF. ![output](https://user-images.githubusercontent.com/31132760/72668198-4d792f80-3a4a-11ea-8412-72cc2e678d9d.gif)

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 src/modules/colorbar/module.js.

See this page for some help in taking your first steps!

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  • If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

  • If you are familiar with the terminal or would like to learn to use it, here is a great tutorial on how to send a pull request using the terminal.

  1. You can also edit files directly in your browser and open a pull request from there.
  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

52 `cy.visit()` Error - DOM Element `id` Attribute Set to `jquery`

Find it on GitHub

Current behavior:

Given a static webpage with zero JavaScript present (no jQuery library), if there exists a DOM element with an id attribute set to jquery (for example, <p id="jquery">jQuery</p>), then the cy.visit() method throws a TypeError: TypeError: item.first is not a function.

![](https://www.dl.dropboxusercontent.com/s/9wkqletdgr30zsb/Screenshot%202020-01-18%2002.31.52.png)

Debug Logs: ``` cypress_runner.js:159529 TypeError: item.first is not a function

Because this error occurred during a 'before each' hook we are skipping the remaining tests in the current suite: 'homepage' at Object.unwrapFirst (http://localhost:5000/cypress/runner/cypress_runner.js:86108:19) at http://localhost:5000/cypress/runner/cypressrunner.js:80941:33 From previous event: at runCommand (http://localhost:5000/cypress/runner/cypressrunner.js:80933:8) at next (http://localhost:5000/cypress/runner/cypress_runner.js:81014:14) From previous event: at http://localhost:5000/cypress/runner/cypressrunner.js:81055:37 From previous event: at run (http://localhost:5000/cypress/runner/cypressrunner.js:81048:19) at Object.cy. as visit at Context.runnable.fn (http://localhost:5000/cypress/runner/cypress_runner.js:81699:24) at callFn (http://localhost:5000/cypress/runner/cypressrunner.js:30929:21) at Hook.../driver/nodemodules/mocha/lib/runnable.js.Runnable.run (http://localhost:5000/cypress/runner/cypress_runner.js:30922:7) at http://localhost:5000/cypress/runner/cypressrunner.js:84876:28 From previous event: at Object.onRunnableRun (http://localhost:5000/cypress/runner/cypressrunner.js:84864:20) at $Cypress.action (http://localhost:5000/cypress/runner/cypress_runner.js:78026:61) at Hook.Runnable.run (http://localhost:5000/cypress/runner/cypressrunner.js:83558:13) at next (http://localhost:5000/cypress/runner/cypressrunner.js:31272:10) at http://localhost:5000/cypress/runner/cypress_runner.js:31294:5 at timeslice (http://localhost:5000/cypress/runner/cypressrunner.js:26362:27) logError @ cypressrunner.js:159529 ```

Added a breakpoint to view the object that's considered a "jQuery object:"

![](https://www.dl.dropboxusercontent.com/s/skb4otgx99ceuj5/Screenshot%202020-01-18%2002.40.12.png)

Desired behavior:

In a previous issue, this type of error was thrown when an older version of jQuery was found on the webpage being tested: https://github.com/cypress-io/cypress/issues/2927. According to the issue thread, it was resolved in Cypress v3.2.0.

I'd expect that a webpage with zero JavaScript present shouldn't encounter this error.

Test code to reproduce

https://github.com/kenchandev/cypress-bug-reduced-test-case

The README.md file will contain directions on how to quickly reproduce this bug.

Versions

Cypress: v3.8.2 Operating System: Mac OS X Browser: Cypress Test Runner's Default Browser

53 Module Selector dropdown showing error in console

Find it on GitHub

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!

What is to be done?

After searching module name in module search input if we clear the input field a error is shown in console, try to remove that error. Refer to below GIF for more info!

![err](https://user-images.githubusercontent.com/42492389/72648050-059dce00-39a0-11ea-9b67-5a7b10be00f5.gif)

Files to refer to: https://github.com/publiclab/image-sequencer/blob/c22c6c70d098715d610c72afe83ef8f6b3d9d57a/examples/lib/defaultHtmlSequencerUi.js#L27

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

54 UI Chatroom Link Should Link to the Gitter Channel

Find it on GitHub

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!

What is to be done?

The UI of ImageSequencer has a link in the footer that leads to one of the general chatrooms on publiclab.org. However, ImageSequencer has its own gitter chatroom now -> https://gitter.im/publiclab/image-sequencer.

You will have to update this link

Files to refer to: 1. https://github.com/publiclab/image-sequencer/blob/d1b9b8beccdbe5ba98cf4e352af103b4913a5fe6/examples/index.html#L221

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify all the files where this code is found.

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

55 Load Image Docs Link Should Not Be Displayed (as it doesn't exist)

Find it on GitHub

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!

What is to be done?

The first step in every sequence of ImageSequencer is the load-image step where the input image is loaded. This is just a sequencer method and not an actual module. It has no dedicated documentation.

All the other modules of ImageSequencer have their own docs here

Even though load-image has no docs, there is a link in the UI for load-image which leads to nothing. ![Screenshot from 2020-01-17 23-35-45](https://user-images.githubusercontent.com/34770591/72636459-1d1b8d80-3985-11ea-9162-c40fe2456cd4.png)

Files to refer to: 1. https://github.com/publiclab/image-sequencer/blob/d1b9b8beccdbe5ba98cf4e352af103b4913a5fe6/examples/lib/defaultHtmlStepUi.js#L48-L50

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify the file defaultHtmlStepUi.js

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

56 Add location modal script to dashboard

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 sidebar/_dashboard in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

At the end of the file add this line: <%= render partial: 'tag/location' %>

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

57 Add a Comment Explaining External Module Definitions

Find it on GitHub

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!

What is to be done?

https://github.com/publiclab/image-sequencer/blob/bfff7e7b999bf256205d412a13f16e154a63beb1/src/Modules.js#L33-L34

In the above code, the commented line imports the invert module from a different repository altogether (using a require statement). This is a powerful feature of ImageSequencer, the modules are independent of the rest of the library's source.

The above example depicts this feature perfectly. You have to add a comment next to the commented code, explaining the feature and the code.

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify the file Modules.js

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

58 .type() does not enter a - or + after a valid number in an input of type number

Find it on GitHub

Current behavior:

Similar to to now closed 6055, if I try to type 123- into an input of type number, the field only contains 123. This is a bit of an edge case, we use these valid characters to make an invalid number to test field validation messages for our NumberTextField component.

This behavior is a discrepancy between Cypress and manual in Chrome as strings like 123- and 1+1 can be entered manually. Our tests are passing in 3.7 but failing in 3.8.2

Desired behavior:

.type() allows valid characters to be added to an input of type number even if the positioning of the characters makes the end value invalid.

Steps to reproduce:

use .type('123-') on an input of type number. use .type('1+1') on an input of type number.

Versions

Chrome 79, Windows 10, Cypress 8.3.2

59 Displayed Version Number is not Visible

Find it on GitHub

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!

What is to be done?

The current version of IS that is used is displayed in the UI at the top right corner but it is not visible. NOTE: The version number has been highlighted manually in the image below. ![Screenshot from 2020-01-12 23-20-07](https://user-images.githubusercontent.com/34770591/72223594-96d30600-3596-11ea-81e1-d35d0ddee9fa.png)

You have to change the appearance of this text to make the text more readable.

Files to refer: 1. https://github.com/publiclab/image-sequencer/blob/12c422a07b55233ae94e13fc3700da2101916c65/examples/demo.js#L38-L42 2. https://github.com/publiclab/image-sequencer/blob/12c422a07b55233ae94e13fc3700da2101916c65/examples/demo.css#L318-L328

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify the file demo.css

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

60 Add command anomaly

Find it on GitHub

js Cypress.Commands.add('getAlias', (alias:string) => cy.get(`@${alias}`));

results in

TypeError: command.get is not a function

but

js Cypress.Commands.add('alias', (alias:string) => cy.get(`@${alias}`));

does not

what trickerypokery?

61 Emails from same research note should display in same thread

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

The issue

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.

The fix

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.

Changes to make in subscription_mailer.rb

Let'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.

Changes to make in comment_mailer.rb

Change 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:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

62 Fix minor typo in LABELS.md

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Changes Requested:

In LABELS.md (https://github.com/publiclab/plots2/blob/master/doc/LABELS.md), there is a typo on line 25: "Issues which need discussion and requirements needs to be elicitated" should be changed to "Issues that need discussion and requirements need to be elucidated"

Please fix this typo.

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

63 Suggest a Python driver conception based on the notebook

Find it on GitHub

Notebook in this repo, is a demonstration of interacting with https://github.com/bacloud14/exec The web service.

In real production environment, this should turn into a Python library, to approach this, there are zillions of ways (writing a driver); The most important consideration, is that not only Python is subject to a driver, many languages will come next, so a basic conception of how an Exce driver should be is very important. Guys that already conceived HTTP clients, you could propose a way to start the implementation.

64 cypress-cli type for CypressRunResult::runs is incorrect (can be null/undefined)

Find it on GitHub

Current behavior:

In the event that the browser fails to connect, the run promise resolves with results which has runs of null or undefined. (Which is likely a separate issue altogether. It should probably not resolve at all - it should reject).

However, the typings indicate that the type of runs is RunResult[] which doesn't match null

Desired behavior:

The type should indicate that runs can be undefined or null, or run() should not resolve on an error running the tests altogether.

Test code to reproduce

  1. Clone https://github.com/xdumaine/cypress-test-tiny
  2. npm i && npm test

65 add function to scrape eclipse

Find it on GitHub

http://metservice.intnet.mu/sun-moon-and-tides-info-eclipses.php

![meteomoris_eclipse](https://user-images.githubusercontent.com/22630684/71894112-cfbe4580-3166-11ea-9ff0-c8fdcb4e3604.png)

get the surrounded text till end as string

66 Add function to scrape cyclone info

Find it on GitHub

![meteomoris_currentcyclone](https://user-images.githubusercontent.com/22630684/71893907-43138780-3166-11ea-8021-8e69cf31c89b.png)

67 Invoke binary directly warning showing always from `cypress verify` (debug mode)

Find it on GitHub

While trying to debug an issue w/ cypress verify getting stuck occasionally (related #6082), I'm getting the following stdout message from running cypress verify in debug mode (via DEBUG=cypress:* yarn cypress verify)

"It looks like you are running the Cypress binary directly. This is not the recommended approach, and Cypress may not work correctly."

Is this is an expected output from the smoke-test?

Current behavior:

`` ❯ DEBUG=cypress:* npx cypress@latest verify cypress:cli installing Cypress from NPM +0ms cypress:cli installing with options {} +0ms cypress:cli version in package.json is 3.8.1 +1ms cypress:cli Reading binary package.json from: /Users/*********/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/Resources/app/package.json +0ms cypress:cli no binary installed under cli version +4ms cypress:cli checking local file /Users/*********/.npm/_npx/47203/lib/3.8.1 cwd /Users/*********/.npm/_npx/47203/lib/node_modules/cypress +0ms cypress:cli preparing to download and unzip version 3.8.1 to path /Users/*********/Library/Caches/Cypress/3.8.1 +0ms cypress:cli needed Cypress version: 3.8.1 +0ms cypress:cli source url https://download.cypress.io/desktop/3.8.1?platform=darwin&arch=x64 +0ms cypress:cli downloading cypress.zip to "/var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip" +0ms cypress:cli Downloading package { url: 'https://download.cypress.io/desktop/3.8.1?platform=darwin&arch=x64', proxy: null, downloadDestination: '/var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip' } +1ms cypress:cli redirect version: 3.8.1 +341ms cypress:cli expected checksum 64ba19b0fe70e5b4eda6dad53c16a8de0234a09871462c510f8e44e5226e5bf17bcbbb87051117aba114bca0f1e875be3ebe1331d4376e8c9f30dac9e11c3c5e +136ms cypress:cli expected file size 167102535 +0ms cypress:cli downloading finished +6s cypress:cli verifying checksum and file size +1ms cypress:cli downloaded file has the expected checksum and size βœ… +505ms cypress:cli finished downloading file: /var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip +7s cypress:cli:unzip unzipping from /var/folders/ds/cwtxfpmd76z4r_g__8r94tbc0000gn/T/cypress.zip +0ms cypress:cli:unzip into /Users/*********/Library/Caches/Cypress/3.8.1 +0ms cypress:cli:unzip zipFile entries count 40147 +7ms cypress:cli:unzip unzipping viaditto` +0ms cypress:cli:unzip unzip completed { yauzlMs: 7, unzipMs: 26116 } +26s cypress:cli removing zip file /var/folders/ds/cwtxfpmd76z4rg8r94tbc0000gn/T/cypress.zip +26s cypress:cli finished installation in /Users/******/Library/Caches/Cypress/3.8.1 +17ms cypress:cli:cli cli starts with arguments ["/usr/local/bin/node","/Users/******/.npm/npx/47203/bin/cypress","verify"] +0ms cypress:cli NODEOPTIONS is not set +0ms cypress:cli:cli program parsing arguments +3ms cypress:cli parsed cli options {} +3ms cypress:cli verifying Cypress app +0ms cypress:cli checking environment variables +1ms cypress:cli checking if executable exists /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/MacOS/Cypress +2ms cypress:cli Binary is executable? : true +1ms cypress:cli binaryDir is /Users/***/Library/Caches/Cypress/3.8.1/Cypress.app +0ms cypress:cli Reading binary package.json from: /Users/***/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/Resources/app/package.json +0ms cypress:cli Found binary version 3.8.1 installed in: /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app +3ms cypress:cli could not read binarystate.json file +3ms cypress:cli {} +0ms cypress:cli is Verified ? undefined +1ms cypress:cli force verify +0ms cypress:cli running binary verification check 3.8.1 +0ms It looks like this is your first time using Cypress: 3.8.1 cypress:cli clearing out the verified version +3ms cypress:cli needs Xvfb? false +0ms cypress:cli spawning, should retry on display problem? false +1ms cypress:cli disabling Electron sandbox +0ms cypress:cli running smoke test +0ms cypress:cli using Cypress executable /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/MacOS/Cypress +0ms cypress:cli smoke test command: /Users/***/Library/Caches/Cypress/3.8.1/Cypress.app/Contents/MacOS/Cypress --no-sandbox --smoke-test --ping=965 +0ms cypress:cli smoke test timeout 30000 ms +0ms β ΄ Verifying Cypress can run /Users/******/Library/Caches/Cypress/3.8.1/Cypress.app cypress:cli smoke test stdout "It looks like you are running the Cypress binary directly.

This is not the recommended approach, and Cypress may not work correctly.

Please install the 'cypress' NPM package and follow the instructions here:

https://on.cypress.io/installing-cypress 965" +2s cypress:cli write verified: true +1ms βœ” Verified Cypress! /Users/*********/Library/Caches/Cypress/3.8.1/Cypress.app ```

Desired behavior:

I did a little digging myself & here what I've found:

  • Cypress prints out the message above when options.invokedFromCli === false https://github.com/cypress-io/cypress/blob/v3.8.1/packages/server/lib/cypress.coffee#L59
  • This options.invokedFromCli is computed based off the options.cwd value https://github.com/cypress-io/cypress/blob/v3.8.1/packages/server/lib/util/args.js#L172
  • This options.cwd is inherited from the --cwd flag, which is injected here https://github.com/cypress-io/cypress/blob/v3.8.1/cli/lib/exec/spawn.js#L84

Based on the findings above, I "believe" this is what's happening under the hood:

  • The cypress verify command runs the a smoke test via runSmokeTest() https://github.com/cypress-io/cypress/blob/v3.8.1/cli/lib/tasks/verify.js#L43
  • runSmokeTest() starts the test by exec'ing the Cypress binary & spawns a child process https://github.com/cypress-io/cypress/blob/v3.8.1/cli/lib/tasks/verify.js#L113
  • Since the binary was exec'ed via the smoke test, the --cwd flag isn't injected
  • Hence the Cypress child-process (spawn'ed from cypress verify) determines that it wasn't being launched directly from the CLI & prints out the message

(From what I've seen so far, seems like this is the intended behaviour & it's harmless since the verify task succeeded.)

Steps to reproduce:

  1. Open a terminal
  2. Run DEBUG=cypress:* npx cypress@latest verify (getting the same output if one were to run DEBUG=cypress:* yarn cypress verify in their project directory)

Versions

Node@LTS (v12.14.0) Cypress@latest (v3.8.1) macOS High Sierra (v10.13.6)

68 Better performance

Find it on GitHub

Note process seems to eat a lot of memory running : ps -o pid,user,%mem,command ax | sort -b -k3 -r These tutorials https://www.valentinog.com/blog/memory-usage-node-js/ https://www.fiznool.com/blog/2016/10/01/running-a-node-dot-js-app-in-a-low-memory-environment/ https://stackoverflow.com/questions/21694567/optimize-node-js-memory-consumption

seems to be very helpful.

69 Better code

Find it on GitHub

Code refactoring: The purpose is to reduced complexity and improve source-code maintainability. Better use of small functions in a modular programming style.

70 Secure and performant code

Find it on GitHub

All code is concerned.

71 "By type" button does not have padding at the right on a tag page

Find it on GitHub

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!

Problem

"By type" button does not have padding at the right ![image](https://user-images.githubusercontent.com/17945250/71669729-45f62d00-2da0-11ea-8d9a-8fd665f9fb76.png) Expected view: ![image](https://user-images.githubusercontent.com/17945250/71669803-8a81c880-2da0-11ea-90cb-7d7d9c4ca148.png)

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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 app/views/tag/show/navtabs.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

Edit line 2. diff - <div class="dropdown" style="margin-top:10px; float:right;"> + <div class="dropdown mr-1" style="margin-top:10px; float:right;">

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

72 Standardise Util Functions Comments

Find it on GitHub

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!

What is to be done?

We are working towards standardizing all the comments in the codebase to make the docs look professional. New developers will get benefitted if we add comments to some of the most commonly used util functions. They are listed below. 1. pixelSetter.js 2. getDefaults.js

You will have to update the comments in the above files based on the guidelines mentioned below. 1. Methods must be described using JSDoc comments 2. Misc code comments should be inline unless it is a long sentence. 3. No use of continuous tenses, no pronouns. 4. No redundant comments. 5. Each comment should start with an uppercase letter and end with a full stop.

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify the file pixelSetter.js

  • [ ] πŸ“ Modify the file getDefaults.js

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

73 Audit SEO of examples and documentation with Lighthouse

Find it on GitHub

Let's figure out performance opportunities of the example and the documentation.

See info on Lighthouse: https://developers.google.com/web/tools/lighthouse#devtools.

After running the tools, create a new issue that details the findings.

74 Homepage modal buttons not scaled

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

:fire: Problem

![Screenshot20191225171442](https://user-images.githubusercontent.com/35997844/71448295-73a4fb80-273a-11ea-84be-331ed93d3924.png)

![Screenshot20191225171519](https://user-images.githubusercontent.com/35997844/71448296-77388280-273a-11ea-972b-1732a7e3cfa0.png)

On mobile phone and tablets, buttons are not of the same height. It results in bad UI/UX and it should be fixed.

🚩 Solution

![Screenshot20191225171912](https://user-images.githubusercontent.com/35997844/71448308-b961c400-273a-11ea-9283-da0d1018c97d.png)

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Open the file ./mapknitter/app/views/front_ui/index.erb

  • Line 55 -> add inline styles to paragraph html <p style="display:flex;justify-content:space-around;"><i style="color:#aaa;">A Community Atlas hosted by <a href="https://publiclab.org">PublicLab</a></i></p>

  • Line 64 -> add an inline style to the anchor tag html <a class="btn btn-primary btn-lg" style="display:flex;align-items:center;justify-content:center;" href="" data-toggle="collapse" data-target="#anonymous-map">

  • Line 66 -> add margin-left to inline styles html <i class="fa fa-plus fa-fw" style="font-size:12px;color:white;margin-left:2%;"></i>

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff $DIFF

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

75 Add Image source to urlHash upon loading an image

Find it on GitHub

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!

What is to be done?

ImageSequencer's UI can read module information from the URL. e.g. https://beta.sequencer.publiclab.org/examples/#steps=contrast{contrast:-31},saturation{} will load a sequence with contrast and saturation. Similarly, a URL containing #src={some-dataurl/link} will start a sequence with a preloaded image. But when a new image is added through the UI, the #src for the image is not added to the URL.

You will have to make it so that the dataURL of the loaded image is added to the URL. Refer: - https://github.com/publiclab/image-sequencer/blob/main/examples/lib/urlHash.js - #src from URL is loaded https://github.com/publiclab/image-sequencer/blob/c370a8b4ea20267462f8fa559608618ca168e457/examples/demo.js#L78-L83 - https://github.com/publiclab/image-sequencer/blob/main/src/ui/LoadImage.js

You can refer to the above files but your final changes will mostly be in the demo.js file. You can make changes to other files if you feel it is necessary.

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify the file demo.js

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

76 Update translations

Find it on GitHub

Update translations in readme.md file.

77 skipTake

Find it on GitHub

Is your feature request related to a problem? Please describe.

When given a number n and an array, returns an array containing every nth element

R.addIndex(R.takeWhile) with specialized predicate can be used to implement this function.

Describe the solution you'd like

```js skipTake(2, [1,2,3,4]); //=> [1, 3]

skipTake(3, _.range(20)); //=> [0, 3, 6, 9, 12, 15, 18] ```

Describe alternatives you've considered

I've considered R.takeWhile, but doesn't exactly do what we want without specialized composition.

Additional context Add any other context or screenshots about the feature request here.

78 isIndexed

Find it on GitHub

Is your feature request related to a problem? Please describe.

To determine if something is an indexed data type. We can start assuming that value is indexed if it's either String or Array type.

Describe the solution you'd like

js isIndexed([1]); //=> true isIndexed('test'); //=> true

Describe alternatives you've considered

Additional context

Originally conceived in https://github.com/char0n/ramda-adjunct/issues/66

79 fnull

Find it on GitHub

Is your feature request related to a problem? Please describe. fnull is in a function that takes a function as an argument and a number of additional arguments, and returns a function that just calls the original function given. The magic of fnull is that if any of the arguments to the function that it returns are null or undefined, then the original β€œdefault” argument is used instead.

Describe the solution you'd like ```js const multiply = (a, b) => a * b; const safeMultiply = fnull(multiply, [1, 1]);

safeMultiply(2, null); //=> 2 ```

Describe alternatives you've considered

https://www.linkedin.com/pulse/function-currying-default-params-javascript-vladim%C3%ADr-gorej/

Additional context Add any other context or screenshots about the feature request here.

80 Improve "About" page

Find it on GitHub

User story

Let's add some info to the About page!

task

Add some team info and some links to GitHub to "About" page.

81 Add example card xml

Find it on GitHub

Follow the instructions in the docs to make an xml file with example cards, and make sure the program works on it!

82 Make the site responsive

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

:fire: Problem

![Screenshot20191220191525](https://user-images.githubusercontent.com/35997844/71281006-1f2a0680-235d-11ea-91bc-cbf9f0155eaf.png)

![Screenshot20191220191502](https://user-images.githubusercontent.com/35997844/71281013-25b87e00-235d-11ea-9d0b-9634dc32266e.png)

The current version of the site is not responsive. :cry: Your job is to make it look great on mobile devices. :iphone:

Don't worry though, it will only take you a few simple edits. πŸ“

🚩 Goal

![Screenshot20191220191935](https://user-images.githubusercontent.com/35997844/71281381-053cf380-235e-11ea-9d71-407e357d48b6.png)

![Screenshot20191220192013](https://user-images.githubusercontent.com/35997844/71281399-0ec65b80-235e-11ea-9847-343e3271add6.png)

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Open image-sequencer/examples/demo.css Below #gif selector(line 154) add this code:

  • line 47 -> remove min-width rule

  • line 69 -> remove min-width rule

css @media(max-width: 768px) { #dropzone { margin: 0 0% 30px; } }

Open image-sequencer/examples/index.html - line 58 remove inline styles from header

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff $DIFF

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

83 Replace dep @types/blob-util (it's deprecated)

Find it on GitHub

Current behavior:

We include @types/blob-util as a dep in the cli here: https://github.com/cypress-io/cypress/blob/v4.0-release/cli/package.json#L64:L64

As mentioned in this PR https://github.com/cypress-io/cypress/pull/5684#pullrequestreview-316174984, this dep has been deprecated since blob-util provides it's own types in their package as mentioned here: https://www.npmjs.com/package/%40types/blob-util

Desired behavior:

Replace use of @types/blob-util to include the types correctly.

Versions

3.8.0

84 cy.wrap does not respect timeout

Find it on GitHub

This example spec file fails with the error below:

js describe('Cypress wait', () => { it('wrap does not wait', () => { cy.wrap( new Promise((resolve) => setTimeout(resolve, 5000)), {timeout: 20000}); }); });

``` Cypress wait 1) wrap does not wait

0 passing (4s) 1 failing

1) Cypress wait wrap does not wait: Error: Cypress command timeout of '4000ms' exceeded. at http://localhost:57838/_cypress/runner/cypressrunner.js:103532:25 ```

Shouldn't cy.wrap respect the timeout option? The test passes if I pass --config defaultCommandTimeout=6000 on the command line, but I want to pass a specific timeout for this cy.wrap command.

85 Add PWA for our reacties application

Find it on GitHub

To implement PWA for our codingAI reactjs application.

86 Add Frequently Asked Questions

Find it on GitHub

Problem

Describe the problem related to this feature request.

I would like to see answers to frequently asked questions.

Solution

What solution do you suggest to solve this problem?

Create the FAQ in the form of a Markdown file.

87 Links on Homepage redirects to 400 Bad Request page

Find it on GitHub

Description

As a user, I need the links on the homepage to be correct, so that I can learn more about AnitaB.org communities.

When clicking some buttons on the homepage, I get redirected to 400 Bad Request, because old website - http://anitaborg.org/ - does not redirect to the current AnitaB official website - https://anitab.org/.

E.g.: http://anitaborg.org/get-involved/systers/systers-initiatives/ should be http://anitab.org/get-involved/systers/systers-initiatives/ (which actually like this, redirects to https://anitab.org/systers/systers-initiatives/)

I think the file that handles this is /develop/systers_portal/templates/common/index.html.

Mocks

What I get right now: ![image](https://user-images.githubusercontent.com/11148726/70841402-0fb53580-1e12-11ea-969c-efcd03be8ecd.png)

Acceptance Criteria

Update [Required]

  • [ ] Make all links on homepage redirect to a valid page instead of 400 Bad Request

Definition of Done

  • [ ] All of the required items are completed.
  • [ ] Approval by 1 mentor.

Estimation

1 hour

88 should('not.be.visible') fails for non visible elements dur to overflow: hidden and set height

Find it on GitHub

Current behavior:

There continues to be issues with visibility tests. I saw the list of issues compiled at https://github.com/cypress-io/cypress/issues/1242 but I am not sure this is one of the issues still listed as open.

In summary: an element that is not visible due to parent overflow: hidden is still reported as visible.

Desired behavior:

Elements not visible due to parent overflow: hidden should be reported as not visible by cypress.

Steps to reproduce: (app code and test code)

Use this code:

``js describe('', () => { before(function() { let html =<!DOCTYPE html>

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin fermentum, velit at eleifend tempus, mi mauris dapibus nunc, vitae semper tellus augue non purus. Suspendisse potenti. Praesent laoreet ornare lorem. Quisque pellentesque tempor magna sit amet facilisis. Pellentesque eleifend dui in nunc tempor, lacinia ullamcorper nunc aliquam. Mauris pretium tincidunt nunc, quis vehicula purus volutpat non. Donec consequat erat velit, nec tincidunt mauris dignissim quis. Sed consectetur, diam dictum feugiat faucibus, dui ex ullamcorper odio, ac rhoncus risus lacus et eros. Sed et vestibulum neque, a viverra felis. Ut quam nisi, dapibus efficitur arcu quis, mollis rhoncus justo. Morbi tristique consectetur tortor. Phasellus posuere, nulla et tempus mollis, est lacus malesuada felis, ac tempor risus ipsum at sapien. Nam ac urna purus. Ut vitae urna ornare, convallis magna vitae, posuere tellus.

Vestibulum

Morbi nisl nunc, tincidunt vel est eu, commodo venenatis lorem. Etiam malesuada sagittis magna, sed suscipit orci tristique vel. Proin vulputate rhoncus dictum. Suspendisse volutpat congue metus, ut egestas magna sollicitudin in. Morbi mollis malesuada urna, vitae laoreet elit rutrum rutrum. Cras at tincidunt justo. Donec varius nisi a dolor vehicula sodales. Quisque eu nisl hendrerit, cursus massa sit amet, convallis nulla. Phasellus dapibus facilisis tellus, sed faucibus mauris gravida ultricies. Sed facilisis efficitur nunc, et vehicula augue dictum ac. Nunc sed ante lorem. Vivamus dapibus ante quis urna dignissim rutrum quis a elit. Nam at mi sit amet felis eleifend ultrices.

Curabitur

In risus ligula, fermentum nec libero eget, faucibus rutrum libero. Proin ligula turpis, porttitor ac nisl pulvinar, aliquet pretium nulla. Aliquam vel porta ante. Nullam dictum enim a justo elementum, et accumsan magna malesuada. Suspendisse lacinia, urna sed egestas scelerisque, lectus arcu congue sapien, quis sollicitudin nibh massa ut lorem. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Sed mattis aliquet libero, ac porta enim sagittis quis. Pellentesque interdum ipsum euismod, sollicitudin est eu, commodo orci. Sed a arcu justo. Sed dignissim, arcu vitae vehicula imperdiet, diam neque pellentesque leo, quis bibendum dolor lectus eu tellus. In faucibus, tellus nec malesuada consectetur, quam dolor pretium diam, at vehicula massa lacus nec ligula. Aliquam ornare, mi in vehicula commodo, sem magna dignissim felis, vel hendrerit erat elit quis nulla.

`; cy.document().then(document => { document.write(html); document.close(); }); });

it('', function() { cy.get('.accordion-content').should('exist').should('not.be.visible'); }); }); ```

Versions

cypress 3.8.0

89 Add Commenting Guidelines to CONTRIBUTING.md

Find it on GitHub

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!

What is to be done?

We are working towards standardizing all the comments in the codebase to make the docs look professional. One of the main steps towards this would be to add some guidelines to the CONTRIBUTING.md file. Some guidelines are listed below (you can add your own too if you feel it is necessary)

  1. Methods must be described using JSDoc comments
  2. Misc code comments should be inline unless it is a long sentence.
  3. No use of continuous tenses, no pronouns.
  4. No redundant comments.
  5. Each comment should start with an uppercase letter and end with a full stop.

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

  • [ ] πŸ“ Modify the file [CONTRIBUTING.md]

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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 it 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

90 Improve application performance

Find it on GitHub

Improve our CodingAI application performance.

91 Add / List the React Component

Find it on GitHub

List out / Add React component for codingAI application and it improve our application.

92 file name contains character ”+β€œ not run

Find it on GitHub

the file cy_web+_20191207220608.js is exsite, but run cypress,

Cannot find module web _20191207220608.js, this character ”+β€œ instead of " ", so not find the file.

Current behavior:

``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Cypress: 3.7.0 β”‚ β”‚ Browser: Electron 73 (headless) β”‚ β”‚ Specs: 1 found (web+20191207220608/web+20191207220608.js) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

────────────────────────────────────────────────────────────────────────────────────────────────────

Running: web+20191207220608/web+20191207220608.js (1 of 1)

Oops...we found an error preparing this test file:

/home/admin/cypress/web _20191207220608/web _20191207220608.js

The error was:

Error: Cannot find module '/home/admin/cypress/web _20191207220608/web _20191207220608.js' from '/home/admin/cypress'

This occurred while Cypress was compiling and bundling your test code. This is usually caused by:

  • A missing file or dependency
  • A syntax error in the file or one of its dependencies

Fix the error in your code and re-run your tests. ```

93 Secure and performant code

Find it on GitHub

I just jumped to JavaScript manipulating Dom and Asyn programming. So I am a n00b x) JS code is executed in client side, so a webmaster is only responsible for the exact first version served to client through the requested URL; However, even for this JS file, I want to be sure it meets minimum security for the client and other endpoints (cdnjs is requested to load JavaScript libraries) All code is concerned.

94 Better code

Find it on GitHub

I just jumped to JavaScript manipulating Dom and Asyn programming. This is very new to me, I know code is very poorly written. There is only one JS file and one HTML file. All code is concerned. Task: code review or pass into : https://jshint.com/

95 Add popover to list authors on wiki page headings

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

What is to be done.

Wiki pages now have this great header showing Authors, Revisions, and the talk page:

![image](https://user-images.githubusercontent.com/24359/70264384-4c27c800-1766-11ea-80aa-168dab23f0c0.png)

Let's make it so you can click the Authors item and see a Bootstrap popover listing the authors' usernames.

The code for that is here:

https://github.com/publiclab/plots2/blob/6d417a384801e4c20b77c4d6360788f19a78b41c/app/views/wiki/_header.html.erb#L34-L36

We can get the authors listing using node.authors, as shown here:

https://github.com/publiclab/plots2/blob/6d417a384801e4c20b77c4d6360788f19a78b41c/app/models/node.rb#L278-L280

And for each one, we could do the following so that their names are clickable and lead to their profile pages!

html <ul> <% node.authors.each do |author| %> <li><a href="/profile/<%= author.username %>">@<%= author.username %></a></li> <% end %> </ul> That code can go inside the popover!

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff $DIFF

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!

96 Convert reactjs into redux component

Find it on GitHub

  1. Convert our reactjs applications into redux applications as separate branch.
  2. We have created the separate folder name as redux-coding-ai and will create the branch.
  3. We have to create the components

97 Add reactjs deployment / build feature

Find it on GitHub

We have create the deployment / build feature or improvement in our codingAI applications .

98 Add contribution list dynamically

Find it on GitHub

Dynamically create the contributions list who participated in our applications like bot create contributions list once we have configure.

99 Add some needed bot for reactjs application

Find it on GitHub

List out useful needed bot for reactjs applications.

100 Update readme file

Find it on GitHub

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!

πŸ€” What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

πŸ“‹ Step by Step

  • [ ] πŸ™‹ 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!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff $DIFF

  • [ ] πŸ’Ύ Commit your changes

  • [ ] πŸ”€ Start a Pull Request. There are two ways how you can start a pull request:

  1. 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.

  2. You can also edit files directly in your browser and open a pull request from there.

  • [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

πŸ’¬β° - 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.

Is someone else already working on this?

πŸ”—- 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!

πŸ€”β“ Questions?

Leave a comment below!