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 Remove geokit-rails gem from the project

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!

πŸ“ Remove the geokit-rails gem from the repository- from Gemfile and Gemfile.lock as it's not used.

πŸ’Ύ Commit your changes

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

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

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

🏁 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!

2 Remove comments

Find it on GitHub

In template.py remove those comments ```python

self.canvas.create_rectangle(20, 50, 200, 100, outline="black", fill="red", width=2, stipple="gray50")

fill("orange")

ircle(10, 10)

``` only for real first-timers

3 Add a text() function

Find it on GitHub

In template.py add a text() function taking

text(<text>, coordinate-x, coordinate-y) so that in snippets it can be called as

text("abc", 20, 20)

4 Remove dependency on username

Find it on GitHub

Username package is notoriously low quality and fails to build. Remove it.

5 Fix typo and remove the "new contributor" tag from the sidebar on profile 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 app/views/users/profile.html.erb in the plots2 repository and edit the line 234 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 - <li class="mt-3"><h5>@<%= @profile_user.name %> <%= @profile_user.new_contributor %> asked</h5></li> + <li class="mt-3"><h5>@<%= @profile_user.name %> has</h5></li>

  • [ ] πŸ’Ύ 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!

6 Tutorial 3 - action_4 button issue

Find it on GitHub

Expected Behavior

When pressing action_4 button I expect to change the state of the action_3 button from enabled to disabled or vice-versa.

Current Behavior

While the state of the action_3 button is changed at the interface layer, it seems like that change is not captured by either implementation or native layers of Toga so pressing the action_3 button always yields the same result - script prints Action 3. Note: while running the app I was printing cmd3.enabled and it changes from True to False or vice-versa when action_4 button is pressed.

Your Environment

I am running Toga on Ubuntu 16.04 with Anaconda Python. Virtual environment is made with conda instead of virtualenv.

  • Python Version - 3.6.8 from --conda-forge channel

  • Operating System and Version (select from the following and list the specific version number; if your OS is not listed, list that as well)

    • [ ] Linux - distro: - version: Ubuntu 16.04
  • Toga Target (the type of app you are trying to generate)

    • [ ] gtk

7 Live editing switch for synchronous editing ability

Find it on GitHub

This is a part of #893

A live editing switch is required somewhere on the sidebar. It could be something like:-

![image](https://user-images.githubusercontent.com/24359/63034696-c2d34980-be87-11e9-9fd0-130a11bab0e0.png) The purpose of this switch is the ability make the map editable by other users connected to the map.

I've started with #937 . Maybe we could extend that accordingly.

We can use the toggle_editing route to save the map creator's preference there.

8 Update Initializers to class factory syntax lll

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.

The problem

What's supposed to happen:

From the official Leaflet docs:

Class Factories You may have noticed that Leaflet objects are created without using the new keyword. This is achieved by complementing each class with a lowercase factory method:

new L.Map('map'); // becomes: L.map('map');

What actually does happen:

We use Leaflet's built-in L.FeatureGroup and L.GeoJSON, but we don't take advantage of their suggested class factory syntax.

Solution

  1. remove the new keyword and change the initializer to L.featureGroup https://github.com/publiclab/mapknitter/blob/204dd5e079e830342510c6ad9b84f78d0a0c55df/app/assets/javascripts/mapknitter/Annotations.js#L10

  2. remove the new keyword and change the initializer to L.geoJSON https://github.com/publiclab/mapknitter/blob/204dd5e079e830342510c6ad9b84f78d0a0c55df/app/assets/javascripts/mapknitter/Annotations.js#L29-L40

Thanks!!

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
    • [ ] 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, an additional checklist will be provided for getting it merged

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.

πŸ’¬ Get help

If you need any help - here are some options:

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

9 Add toString methods to API interface implementations

Find it on GitHub

I'm marking this issue for first-timers-only. That means that I will only accept a PR for this one from someone who's never contributed to open source before. This one is easy (but don't make that statement make you feel bad if you have a hard time with it, there's more to contributing to open source than changing lines of code, especially if it's your first time). I'll hold your hand through this if you need me to. :-)

We'd like to add toString() methods to all of the API classes, with the implementation in the associated Abstract class for interfaces. This has been done for AbstractOperatingSystem, AbstractDisplay, AbstractOSVersionInfoEx, AbstractSoundCard, AbstractUsbDevice, AbstractCentralProcessor, and the class OSProcess

Similar implementations should be made for: - [x] ComputerSystem - [x] Baseboard - [x] Firmware - [x] GlobalMemory - [x] VirtualMemory - [x] HWDiskStore - [x] HWPartition - [ ] NetworkIF - [x] PowerSource - [x] Sensors - [ ] OSFileStore - [ ] NetworkParams

Feel free to do one, or multiple implementations! Comment below which one(s) you are doing to avoid stepping on someone else's toes.

Here are the steps to get a PR merged here. - Read the CONTRIBUTING file for reference. I'll walk you through anything you don't understand. - Fork the project to your own GitHub account, make a local clone, and create a branch for your submission. - Look at how this class's information is displayed in the SystemInfoTest class. This is a suggested starting point for the toString() implementation. - For interfaces, create a toString() method in the Abstract class implementing the interface. See the above links for examples. - For classes, create the toString() method in the class. - Alter the code in the SystemInfoTest class to call the toString() method you just created. - Commit your changes, push to to your GitHub fork, and create a Pull Request - Respond to the usually minor comments on code review - Celebrate! :tada:

10 Handle browser not found object better

Find it on GitHub

v3.4.1 - a browser not found error does not understand that it gets an object, not a name

```coffeescript throwBrowserNotFound(nameOrPath, browsers)

throwBrowserNotFound = (browserName, browsers = []) -> names = .map(browsers, "name").join(", ") debug("BROWSERNOTFOUNDBYNAME %o available browser names %o", browserName, names) errors.throw("BROWSERNOTFOUNDBY_NAME", browserName, names) ```

cypress:server:browsers selecting browser launcher for family electron-app +0ms cypress:server:browsers BROWSER_NOT_FOUND_BY_NAME { displayName: 'cypress-example-electron', family: 'electron-app', info: 'Electron.js app that supports the Cypress launcher', isChosen: true, majorVersion: '99', name: 'cypress-example-electron', path: '/Users/gleb/git/cypress-example-electron', version: '0.0.0', isHeaded: true, isHeadless: false } available browser names 'chrome, canary, cypress-example-electron'

11 Replace rawgit links with links to a non-deprecated CDN

Find it on GitHub

the Getting-Started.md file has some links to rawgit - but rawgit is deprecated and will be discontinued, possibly as soon as October 2019. We should use a different CDN link instead - the rawgit homepage has several suggestions.

12 [easy issue] mark up all code examples as javascript code blocks

Find it on GitHub

In this repository we have several markdown files with examples in code blocks, denoted by three backticks in the code. These examples are all javascript, so it would be nice to enable syntax highlighting by specifying that the examples are javascript.

example someJavascriptFunction(function() { var thingy = 12; }); vs javascript someJavascriptFunction(function() { var thingy = 12; });

13 Random Colour plugin description

Find it on GitHub

In the README.md file I saw "Random Color" under "To-do plugins". I think I can make this plugin, but I wanted to get a more detailed description of what this plugin needs to do if possible.

14 Integration with Dev.To

Find it on GitHub

There is a lot of pending documentation here to describe the wonderful features of QCObjects. So a blowing idea came to mi mind. Why not write all the related articles in a selected network like Dev.To and take these contribution articles automatically downloaded and processed to a centralised documentation website?

Dev.To has a simple and incredible REST API to do so, and using the link bellow, it is possible to get all the QCObjects related in Dev.To (just a few right now, I expect you can help me as well writing new articles :) ):

https://dev.to/api/articles?tag=qcobjects

The alternatives are: 1.- An automated side menu component injected in the main reference page. 2.- A complete other website with the automated documentation knowledge base.

Have a look at the MarkdownController in the file https://github.com/QuickCorp/QCObjects/blob/master/doc/js/cl.quickcorp.controller.js to know how to implement an automated markdown component

15 Wordpress Integration

Find it on GitHub

+24 million of live websites are using Wordpress (source: BuiltWith)

So it is a good chance to expand the QCObjects users community if they can integrate QCObjects into their WP website in just a click to activate a plugin.

The ways we can go through are two: 1.- Creating a theme using the QCObjects New App template. 2.- Creating a plugin using the QCObjects New App template.

16 Updating code snippets for Visual Studio Code

Find it on GitHub

QCObjects has snippets integration with VSCODE, which is one of the most used IDE's

Find out more of the QCObjects VSCODE extension here:

https://marketplace.visualstudio.com/items?itemName=Quickcorp.QCObjects-vscode

Your help is needed to keep the snippets up to date. If you got any feature advance proposal to enrich the extension you are very welcome as well!

Thanks

17 Updating snippets for Atom

Find it on GitHub

Please I need to update the snippets for Atom. Your code contributions are very welcome! Learn more about Atom here:

https://atom.io

And learn more about QCObjects Atom extension here:

https://atom.io/packages/qcobjects-syntax

It is needed a way to synchronise the versioning of both packages, as well as updating the snippets to the last version of QCObjects.

If you got any proposal about how to enrich the extension for Atom you are very welcome as well!

Thanks

18 Check vi (TiαΊΏng Việt) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 188vilocale
  • Commit and create PR

19 Check tr (TΓΌrk) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 187trlocale
  • Commit and create PR

20 Check th (ΰΉ„ΰΈ—ΰΈ’) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 186thlocale
  • Commit and create PR

21 Check ru (Русский) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 185rulocale
  • Commit and create PR

22 Check ro (RomÒnă) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 183rolocale
  • Commit and create PR

23 Check pt (PortuguΓͺs) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 182ptlocale
  • Commit and create PR

24 Check pl (Polskie) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 181pllocale
  • Commit and create PR

25 Check ms (Melayu) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 180mslocale
  • Commit and create PR

26 Check ko (ν•œκ΅­μ–΄) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 179kolocale
  • Commit and create PR

27 Check ja (ζ—₯本人) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 178jalocale
  • Commit and create PR

28 Check it (Italiano) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 177itlocale
  • Commit and create PR

29 Check id (Bahasa) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 176idlocale
  • Commit and create PR

30 Check hi (ΰ€Ήΰ€Ώΰ€‚ΰ€¦ΰ₯€) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 175hilocale
  • Commit and create PR

31 Check fr (Français) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 174frlocale
  • Commit and create PR

32 Check es (EspaΓ±ol) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 173eslocale
  • Commit and create PR

33 Check el (Ελληνικά) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 172ellocale
  • Commit and create PR

34 Check de (Deutsche) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 171delocale
  • Commit and create PR

35 Check cn (δΈ­ζ–‡) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 170cnlocale
  • Commit and create PR

36 Check bn (বাঙালি) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 169bnlocale
  • Commit and create PR

37 Check bg (Π‘ΡŠΠ»Π³Π°Ρ€ΡΠΊΠΈ) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 168bglocale
  • Commit and create PR

38 Check en (English) locale and fix typos

Find it on GitHub

Check locales by native and fix typos.

Project use jekyll-multiple-languages-plugin. Each locale file are keeped in _18n folder. For example en is located in _18n/en.yml file.

Project was translated by translation service not by human. So it can keep typos.

Need to check current issue language.

  • Fork
  • Create branch 167enlocale
  • Commit and create PR

39 Display Image bars in a single line

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 In /about Image-bar is not displayed on a single line. Its right end of the scale is carried forward to the bottom line. i.e cm/px is displayed on the next line. So as to remove it, decrease the width of the Map-bar. To do this, In change 100 to 160 https://github.com/publiclab/mapknitter/blob/3ca0b08749d31d9f354518ae29ece4690a1248ca/app/views/maps/_statistics.html.erb#L26

![Selection_219](https://user-images.githubusercontent.com/32747809/62319748-4ff7c500-b4bc-11e9-8b1c-8175447420b4.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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

40 Map-bars not displayed in a single line

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 In /about Map-bar is not displayed on a single line. Its right end of the scale is carried forward to the bottom line. i.e cm/px is displayed on the next line. So as to remove it, decrease the width of the Map-bar. To do this, In change 100 to 160 https://github.com/publiclab/mapknitter/blob/3ca0b08749d31d9f354518ae29ece4690a1248ca/app/views/maps/_statistics.html.erb#L23

![Selection_218](https://user-images.githubusercontent.com/32747809/62319528-ccd66f00-b4bb-11e9-911e-2dbe596584be.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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

41 PHP: send to all

Find it on GitHub

42 PHP: implement hashing

Find it on GitHub

Password comparison currently does not implement hashing.

43 Add TODO list

Find it on GitHub

A todo section. You can add, modify and delete items. You can also cross out items.

44 The file `app/views/like/_like.html.erb` is not properly indented, indentation needs to be unformised.

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!

45 [feature] dark mode for specs manager window

Find it on GitHub

Current behavior:

Currently, specs-listing window is very bright:

![Screen Shot 2019-07-29 at 05 33 46](https://user-images.githubusercontent.com/8344688/62022161-d06bac80-b1c2-11e9-94e9-c93e31e17c85.png)

Desired behavior:

Would it be technically possible to make a dark mode for it? It could be switchable automatically via media query prefers-color-scheme or manually, in Settings tab.

Steps to reproduce: (app code and test code)

n/a

Versions

Cypress 3.4.0 Chrome 75 MacOS Mojave 10.14.6

46 Update initializers to class factory syntax

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.

The problem

What's supposed to happen:

From the official Leaflet docs:

Class Factories You may have noticed that Leaflet objects are created without using the new keyword. This is achieved by complementing each class with a lowercase factory method:

new L.Map('map'); // becomes: L.map('map');

What actually does happen:

We use built-in Leaflet classes such as L.Control.Layers, L.Map, and L.LatLng, but we don't take advantage of their suggested class factory syntax. Let's clean up the below file a bit to do that:

Solution

  1. remove the new keyword and change the initializer to L.map https://github.com/publiclab/mapknitter/blob/fb876407671f27e0bc97cb9da1edb2baa8797ac0/app/views/map/_leaflet.html.erb#L57

  2. remove the new keyword and change the initializer to L.control.layers https://github.com/publiclab/mapknitter/blob/fb876407671f27e0bc97cb9da1edb2baa8797ac0/app/views/map/_leaflet.html.erb#L70

  3. remove the new keyword and change the initializer to L.latLng https://github.com/publiclab/mapknitter/blob/fb876407671f27e0bc97cb9da1edb2baa8797ac0/app/views/map/_leaflet.html.erb#L73

Thanks!!

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
    • [ ] 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, an additional checklist will be provided for getting it merged

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.

πŸ’¬ Get help

If you need any help - here are some options:

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

47 Align features in homepage to left instead of center

Find it on GitHub

I'm submitting a ... - [ ] bug report - [x] feature request

Description : <!-- Describe your feature --> Align the features portion text to the left Current behaviour: <!-- How the bug manifests. --> Aligned center Expected behaviour: <!-- Behaviour would be without the bug. --> Aligned to the left Steps to reproduce: Go to badgeyay.com

Screenshots <!--Please include relevant Screenshots related to the bug or the feature request. --> ![Screenshot from 2019-07-28 01-44-44](https://user-images.githubusercontent.com/8947010/61999200-8a86e980-b0d9-11e9-8e15-720f16c2219e.png)

Would you like to work on the issue? <!-- Please let us know if you can work on it or the issue should be assigned to someone else. --> No. first-timers only-please

48 Optional values: bearer and sendImmediately are missing in Cypress.Auth interface (TypeScript)

Find it on GitHub

Current behavior:

The current interface for Auth:

js interface Auth { username: string; password: string; }

Desired behavior:

Both bearer and sendImmediately should be optional props:

js interface Auth { username: string; password: string; bearer?: string; sendImmediately?: boolean; }

Steps to reproduce: (app code and test code)

Try passing either bearer or sendImmediately as options

Versions

Cypress 3.3.2

49 Stub / spy counter badge is cut off

Find it on GitHub

Cypress 3.4.0 with Electron or Chrome

Recipe in https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/stubbing-spying__window

Run the spec file and after it is finished click on the button "Open new window" inside the application frame (like a user). The cy.stub counter keeps incrementing - and the badge appears, but the badge gets cut off on the left.

Relevant markup

Relevant files: - packages/reporter/src/commands/command.jsx - packages/reporter/src/commands/commands.scss

50 Document keyboard shortcuts for Test Runner

Find it on GitHub

I'm submitting a...

[ ] Bug report [x] Content update [ ] Process update (build, deployment, ... )

Type of bug / changes

As per https://github.com/cypress-io/cypress/pull/3943 there will be new keyboard shortcuts in the Test Runner.

  • Press r to rerun tests
  • Press s to stop tests
  • Press f to focus on the specs window

This should be documented in the Test Runner doc: https://github.com/cypress-io/cypress-documentation/edit/develop/source/guides/core-concepts/test-runner.md

51 Complete docstrings in main.py

Find it on GitHub

Currently there are incomplete or example docstrings in main.py in Google style, see here.

The task would be to understand the code in main.py and document it properly, following our guide here. This will require some time since you'll need to understand the code but it is (in my opinion) a good introductory to the project.

If you have any questions or problems regarding the task or the documentation guide let me know or ask on our discord!

52 Fix a typo in the demo

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

  • [ ] πŸ’Ύ Commit your changes

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

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

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

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

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

53 Redesign Add Graph Button

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.

Problem

The current Add Graph button is a simple bootstrap primary button. ![image](https://user-images.githubusercontent.com/40794215/61634910-02a37880-acb0-11e9-9715-aeac5f9a9e4f.png)

πŸ“‹Solution

<button type="button" class="btn btn-primary" id=' + this.addGraphButtonId + '> Add Graph</button>

Change the above line in

https://github.com/publiclab/simple-data-grapher/blob/fa222a480c402d15d260f70cb42c23694577e603/src/View.js#L347

By adding some styling, probably a fa fa-icon or some other color!

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

  • [ ] πŸ’Ύ 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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

54 Removing unused code

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.

Problem

Some of the code which was previously written is not required anymore.

πŸ“‹Solution

Remove <button type="button" class="btn btn-success" id=' + this.gsheetId + '> Export as Google </button><div class="g-signin2" data-onsuccess=' + this.onSignIn + '></div> at line https://github.com/publiclab/simple-data-grapher/blob/fa222a480c402d15d260f70cb42c23694577e603/src/View.js#L347

and

https://github.com/publiclab/simple-data-grapher/blob/fa222a480c402d15d260f70cb42c23694577e603/src/View.js#L113-L115

in https://github.com/publiclab/simple-data-grapher/blob/main/src/View.js

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

  • [ ] πŸ’Ύ 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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

55 PHP: Add drawer in admin panel

Find it on GitHub

see files in admin/

56 The graph div should be made 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.

πŸ“‹ 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

  • [ ] πŸ’Ύ Commit your changes

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

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

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

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

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

57 appointment_add allows historic dates.

Find it on GitHub

![add_appointment](https://user-images.githubusercontent.com/33946380/61370692-f2903100-a88a-11e9-8490-30f3e5250b05.gif)

58 Flask: Add people section

Find it on GitHub

add another view -> people, see products or appointments and do the same | any help needed ask!

People need the following: - Name - Surname - Age - Info

Others as needed

You are expected to add an icon in nav.

59 Document Noise-Reduction Module

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!

To gain a sense of what the issue targets go to MODULES.md , we need to add documentation for Noise-reduction module. You can go and have a look at the module here to see the types of processing supported.

  • [ ] πŸ“ Update the following file

1. MODULES.md and add documentation for Noise Reduction Module

  • [ ] πŸ’Ύ 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!

Please show us where to look

https://beta.sequencer.publiclab.org

What's your PublicLab.org username?

This can help us diagnose the issue:

Browser, version, and operating system

Many bugs are related to these -- please help us track it down and reproduce what you're seeing!


Thank you!

Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.

To learn how to write really great issues, which increases the chances they'll be resolved, see:

https://publiclab.org/wiki/developers#Contributing+for+non-coders

60 Make each executed program start in a new console

Find it on GitHub

Currently each program executes on the launcher's console itself, make it such that each executed program executes in it's own console. Hint: execute python file from python. But you see what fits in.

61 Cypress is not able to clean /screenshots

Find it on GitHub

Current behavior:

On every run, cypress will clean it's screenshots folder (as mentioned in the documentation). Unfortunately on Windows it is likely that the filenames are too long and thus can not be deleted. When cypress tries to do this, it ignores those files. We take all screenshots after the test runs and publish them as build artifacts. So this is a problem as we always see old screenshots.

Desired behavior:

Cypress should be able to delete them anyway.

I will use a own build step that uses "rimraf" to do this. maybe cypress should include rimraf or similar for this task?

Steps to reproduce: (app code and test code)

https://github.com/gabbersepp/cypress-test-tiny

Execute cypress from this repo on a Windows 2016 Server.

Please note: It seems that Windows 10 has increased it's max path length. So when using this repo on a Win10 machine, you will have no issues.

Versions

cypress 3.3.2 Windows 10 Chrome: Version 75.0.3770.100 (Offizieller Build) (64-Bit)

62 Add theming support - bootstrap

Find it on GitHub

If you know bootstrap, try implementing theming. See screenshots, currently it's black, it'll be a nice challenge to implement theming in a flask app. Gurl, get those grey matters running

63 Missing information about git branch in cypress dashboard runs for CodeFresh

Find it on GitHub

Much like similar issues, the cypress dashboard isn't getting the git info from the CI runs in CodeFresh:

![image](https://user-images.githubusercontent.com/2730609/60373427-fb40c600-99b4-11e9-805b-8608229cd203.png)

Help troubleshooting this would be appreciated! Thanks!

64 Add more messages

Find it on GitHub

Add more messages to the current array. Try to make them friendly, nice things that would make your day a little bit better. You can use emojis. They shouldn't be too long.

65 Add a prop to send custom messages

Find it on GitHub

Introduce a prop. The prop will receive an array/collection of messages that will be appended to the messages array, and potentially be part of the returned random message.

66 Cypress fails to parse environment variables with commas

Find it on GitHub

Current behavior:

Cypress fails to run when passing an environment variable containing a comma.

Command run: cypress open --env ABC="1,2,3"

Stacktrace:

A JavaScript error occurred in the main process Uncaught Exception: TypeError: Cannot read property 'split' of undefined at pipesToCommas (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/lib/util/args.js:95:14) at JSONOrCoerce (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/lib/util/args.js:115:9) at /home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:13402:38 at /home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:4911:15 at baseForOwn (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:2996:24) at Function.mapValues (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:13401:7) at /home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:4374:28 at arrayReduce (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:683:21) at baseWrapperValue (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:4373:14) at LodashWrapper.wrapperValue (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/nodemodules/lodash/lodash.js:9052:14) at sanitizeAndConvertNestedArgs (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/lib/util/args.js:151:4) at Object.toObject (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/lib/util/args.js:227:21) at Object.start (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/lib/cypress.js:77:40) at Object. (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/index.js:27:43) at Object. (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/packages/server/index.js:29:3) at Module.compile (module.js:642:30) at Object.Module.extensions..js (module.js:653:10) at Module.load (module.js:561:32) at tryModuleLoad (module.js:504:12) at Function.Module.load (module.js:496:3) at Module.require (module.js:586:17) at require (internal/module.js:11:18) at Object. (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/index.js:2:1) at Object. (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/app/index.js:3:3) at Module.compile (module.js:642:30) at Object.Module.extensions..js (module.js:653:10) at Module.load (module.js:561:32) at tryModuleLoad (module.js:504:12) at Function.Module.load (module.js:496:3) at Object. (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/electron.asar/browser/init.js:186:8) at Object. (/home/ehlerts/.cache/Cypress/3.3.1/Cypress/resources/electron.asar/browser/init.js:188:3) at Module.compile (module.js:642:30) at Object.Module.extensions..js (module.js:653:10) at Module.load (module.js:561:32) at tryModuleLoad (module.js:504:12) at Function.Module.load (module.js:496:3) at Function.Module.runMain (module.js:683:10) at startup (bootstrapnode.js:196:16) at bootstrap_node.js:622:3

Once the stacktrace has been printed, nothing happens.

Desired behavior:

Cypress should be able to parse environment variables containing commas.

Steps to reproduce: (app code and test code)

Run the following from a terminal:

cypress open --env ABC="1,2,3"

Versions

Tested Cypress versions: 3.3.1, 3.2.0, 3.1.5 Operating system: Ubuntu 18.04.2 LTS

67 Having a dedicated command to show up local environment information 'cypress info'

Find it on GitHub

Feature Request

Most CLI tools these days are shipped with a dedicated info command which shows up local environment information. Also, the present issue template includes a section which expects to have information regarding the local environment.

With this all the user has to do is just copy and paste the information as shown by cypress info within the respective section.

68 Resolve linting errors

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.

Problem

πŸ“‹Solution

  • [ ] πŸ™‹ 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 ``` // install ESLint $ npm i -g eslint

// navigate and run linter $ cd simple-data-grapher && eslint --fix .

// format code to fix linting errors ``` After the errors are fixed, proceed as specified below.

  • [ ] πŸ’Ύ 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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

69 On cy.visit('file://...) throw err to explain they should visit relative html file

Find it on GitHub

Current behavior:

We've had a couple people try to cy.visit('file://...). We support visiting .html files by specifying the relative path.

  • https://github.com/cypress-io/cypress/issues/4450
  • https://github.com/cypress-io/cypress/pull/4293

Desired behavior:

We can see if the user has passed in a file:// and throw a specific error advising them to pass in the relative path to the file from their projectRoot.

Versions

Cypress 3.3.1

70 Remove redundant function from community-toolbox.js

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 community-toolbox.js in the community-toolbox 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:

CHANGES

  • In src/scripts/community-toolbox.js,

diff $DIFF - function displayIssuesForRepo(org, repo, label, selector) { - toolbox.api.Issues - .getIssuesForRepo(org, repo, { qs: { labels: label } }) - .then(function onGotIssues(issues) { - issues.forEach(function(issue) { - toolbox.issuesUI.insertIssue(issue, selector); - }); - }); - }

After doing these changes, run grunt build before making a commit

  • [ ] πŸ’Ύ 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!

71 Add badges

Find it on GitHub

Add badges similar to flip-remote

72 Cypress.dom.isDetached missing from Typescript types

Find it on GitHub

Current behavior:

The method Cypress.dom.isDetached() type errors in Typescript projects.

Desired behavior:

The method Cypress.dom.isDetached() does not type error in Typescript projects.

Steps to reproduce: (app code and test code)

  1. Set up a Typescript Cypress project as described in https://docs.cypress.io/guides/tooling/typescript-support.html
  2. Write the following test:

```Typescript describe('Demonstrates bug', function() { beforeEach(() => { cy.setup(); });

it('demonstrates Typescript error'), function() { cy.get('button').then(($el) => { Cypress.dom.isDetached($el) }); }); }); 3. Get the following error: Property 'isDetached' does not exist on type '{ isHidden(element: HTMLElement | JQuery): boolean; }' ```

Versions

Cypress 3.2.0 Typescript 3.4.5 Chrome 74.0.3729.169 macOS 10.14.5

73 Issue template

Find it on GitHub

Please if you got any issue follow this template:

========

Purpose: Name of your purpose or proposal. Example: Compliance with ECMA 262

Feature: feature (existing or new) that you want to affect with this issue. Examples are: Nested components stack, dynamic components load. Dynamic complex cache control, etc.

Artifact: The artifact that you are affecting, touching , involving with this issue . Examples: Component Tag, Component Class, Controller, View, Effect, Import, Export, global scope... etc

Priority: how concerned are you about this issue: High priority, low priority, middle priority. (Please no other values here)

Changes: the code. Please put here a piece of code you want to simplify or improve. You’re free to fork QCObjects for your own needs but I highly recommend you to spend some time standardizing. We review everything and test everything almost everywhere we can before to put in action a code change. And it’s because we want to make QCObjects a really professional tool, not just another β€œJavaScript something”. We want your projects to be listed in the best quality line lists. So please let us reject some proposals in order to make this happen. Thanks

============

Issues will not be deleted unless they not meet the GitHub code of conduct.

All the issues will be answered as soon as possible.

Please try to read the issues first before to put a new one.

74 IRC <=> Discord bridge

Find it on GitHub

Since Discord is quite popular alternative for chatting it will be nice to make a plugin that allows bridging two channels.

For example:

IRC on Discord and specific channel on IRC that have this bot.

Requirements: * Discord API key * Ability to list online people on IRC * Ability to list people on Discord (with marks near online nicknames) * Ability to mention people both sides

75 [FTO] Refactor EXIF conditionals

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 below conditionals according to proper logic, i.e., remove redundant if-elsees, or use 'or' || operators to combine them if their logic is identical. https://github.com/publiclab/mapknitter/blob/cc7e9242f559ee53b581f94c8b43adfcc8c28229/app/assets/javascripts/mapknitter/Map.js#L328-L332 https://github.com/publiclab/mapknitter/blob/cc7e9242f559ee53b581f94c8b43adfcc8c28229/app/assets/javascripts/mapknitter/Map.js#L319-L322 https://github.com/publiclab/mapknitter/blob/cc7e9242f559ee53b581f94c8b43adfcc8c28229/app/assets/javascripts/mapknitter/Map.js#L308-L312

  • [ ] πŸ’Ύ 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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

76 Make Select a module functionality 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.

πŸ“‹ Step by Step

Currently the "Select a module" button is not responsive at all. What we want in this issue is to make that reponsive. This is a simple UI part and the files that can be referred to are:

demo.css selectize.default.css - [ ] πŸ™‹ 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!

  • [ ] πŸ’Ύ 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!

77 Add a way to clear selection with `cy.select()`

Find it on GitHub

This Stack Overflow question points out that cy.select() can't clear a selection, and apparently, neither can commands like cy.clear(): https://stackoverflow.com/questions/56340978/how-do-i-clear-a-select-input-using-cypress

Things that should work, but don't:

  • cy.select([]) should cause no elements to be selected
  • cy.clear() with a <select> subject should cause no elements to be selected

Also, maybe cy.select() or cy.select(undefined) should also clear the selection.

78 Solve no-undef errors

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!

To gain a sense of what the issue targets go to .eslintrc.js and comment the no-undef': 0 rule and the go to your terminal and run below command. npx eslint . You will see a list of no-undef errors and by this issue we plan to reduce those errors.

  • [ ] πŸ“ Update the following files
  1. ReplaceImage.js add const $ = window.$; at line 4 in ReplaceImage()
  2. Ui.js add const $ = window.$; at line 3 in CropModuleUi()
  3. Crop.js and modify line 20 as diff -backgroundColor = options.backgroundColor.split(' '); +var backgroundColor = options.backgroundColor.split(' ');
  4. Module.js and change line 7 ```diff
  5. getPixels = require('get-pixels');
  6. var getPixels = require('get-pixels'); ```
  7. Module.js and add as ```diff function extraManipulation(pixels) {
  8. const $ = window.$; var i = 0, sum = [0, 0, 0, 0]; ```
  9. Module.js as ```diff -rdata = pixels.get(i, j, 0); +var rdata = pixels.get(i, j, 0), rnewdata = (255 / r) * rdata; pixels.set(i, j, 0, rnew_data);

-gdata = pixels.get(i, j, 1); +var gdata = pixels.get(i, j, 1), gnewdata = (255 / g) * gdata; pixels.set(i, j, 1, gnew_data);

-bdata = pixels.get(i, j, 2); +var bdata = pixels.get(i, j, 2), bnewdata = (255 / b) * bdata; pixels.set(i, j, 2, bnew_data); ``` 7. Convolution.js

```diff -for (i = 0; i < 9; i++) { +for(var i=0; i < 9; i++) { kernelValues[i] = Number(kernelValues[i]) * constantFactor; } -for (y = 0; y < 3; y++) { +for (var y = 0; y < 3; y++) {

-for (x = 0; x < 3; x++) { +for(var x = 0; x < 3; x++) {

As explained similar changes can be made for many others files to bring down the number of errors (no-undef) for files [SetInputStep](https://github.com/publiclab/image-sequencer/blob/main/src/ui/SetInputStep.js), [Module.js](https://github.com/publiclab/image-sequencer/blob/main/src/modules/WebglDistort/Module.js), and many others. The errors can be seen in the terminal using npx eslint . ``` and similar changes can be made in files.

  • [ ] πŸ’Ύ 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!

79 Change cursor to pointer

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

![Selection_162](https://user-images.githubusercontent.com/32747809/58415913-989a9880-809d-11e9-8b62-74ac0840a6b9.png)

Changes: Chance cursor to pointer download and pan to this image Make changes in file app/views/images/index.html.erb Change https://github.com/publiclab/mapknitter/blob/dc96adae1b376e7a90a3410c535dd547230caf5e/app/views/images/index.html.erb#L42 https://github.com/publiclab/mapknitter/blob/dc96adae1b376e7a90a3410c535dd547230caf5e/app/views/images/_index.html.erb#L43 - [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 :)

πŸ€”β“ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

80 Fix Rubocop performance deprecation warning

Find it on GitHub

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

Problem:

Performance cops have been removed from RuboCop 0.68

πŸ“ Update:

Put this in Gemfile.

gem 'rubocop-performance'

Then add this in .rubocop.yml.

yaml require: rubocop-performance

After changing run bundle install

  • [ ] πŸ’Ύ 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 :)

πŸ€”β“ Questions?

Leave a comment below!

81 Add code sandbox links to the documentation

Find it on GitHub

82 document.referrer is set on cy.visit(...)

Find it on GitHub

Current behavior:

document.referrer is set to cypress test url when I use cy.visit(...)

Desired behavior:

document.referrer is an empty string

Steps to reproduce: (app code and test code)

js cy.visit('https://your.test.dom/') jscode on the page:

console.log(document.referrer)

Versions

3.3.1 cypress (chromium 73 and electron 61) Kubuntu 18.04

83 Crash when plugins event handler is undefined

Find it on GitHub

Bug

Crashes in 3.2.0 and 3.3.0, have not tried earlier versions Mac

Reproduction in https://github.com/cypress-io/cypress-test-tiny/tree/no-plugins-export

npm install npm run cypress:open and click on spec file

Reproduction

Register undefined event handler in plugins.js file for an event like

js module.exports = (on, config) => { // `on` is used to hook into various events Cypress emits // `config` is the resolved Cypress config on('file:preprocessor') }

and get the following crash

Stack trace in the terminal

GET /__cypress/tests?p=cypress/support/index.js-383 200 8.371 ms - 146 TypeError: event.handler is not a function at invoke (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/run_plugins.js:17:16) at /Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/util.js:48:16 at tryCatcher (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/node_modules/bluebird/js/release/util.js:16:23) at Function.Promise.attempt.Promise.try (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/node_modules/bluebird/js/release/method.js:39:29) at Object.wrapChildPromise (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/util.js:47:28) at Object.wrap (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/preprocessor.js:25:8) at execute (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/run_plugins.js:80:20) at EventEmitter.ipc.on (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/run_plugins.js:136:5) at emitThree (events.js:136:13) at EventEmitter.emit (events.js:217:7) at process.<anonymous> (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/util.js:25:29) at emitTwo (events.js:126:13) at process.emit (events.js:214:7) at emit (internal/child_process.js:772:12) at _combinedTickCallback (internal/process/next_tick.js:141:11) at process._tickCallback (internal/process/next_tick.js:180:9) GET /__cypress/tests?p=cypress/integration/spec.js-143 200 8.418 ms - 146

It would be nicer to have a much better error message here

84 Add Leaflet FullHash object for dynamic URL

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

We have added leaflet-fullHash library in the bower and included the link to this library on the index page .

Let's add leaflet-fullHash object which makes the URL dynamic in accordance to selected layers of the map .

Add this lines of code after this line https://github.com/publiclab/mapknitter/blob/9aac51944a212e9c1c2cda06406c11f630d9c10a/app/views/maps/index.html.erb#L205 in index.html.erb :

```js var allMapLayers = { "BL1": baselayer1, "Purple": PurpleAirMarkerLayer, "STruth": SkyTruth, "FracTL": Fractracker, "ToxicR": ToxicRelease, "OdorR": OdorReport, "MapK": MapKnitter, "OIMPower": OpenInfraMapPower , "OIMapTelecom": OpenInfraMapTelecom , "OIMPetroleum": OpenInfraMapPetroleum , "OIMWater": OpenInfraMapWater , "JMincome": Justicemapincome, "JMamericanIndian": JusticeMapamericanIndian , "JMasian": JusticeMapasian , "JMblack": JusticeMapblack, "JMmulti": JusticeMapmulti , "JMhispanic": JusticeMaphispanic , "JMnonWhite": JusticeMapnonWhite, "JMwhite": JusticeMapwhite , "JMplurality": JusticeMap_plurality , "Clouds": clouds , "cloudsclassic": cloudscls , "precipitation": precipitation , "precipcls": precipitationcls , "rain": rain , "raincls": raincls , "snow": snow , "pressure": pressure , "pressurecontour": pressurecntr , "temp": temp , "wind": wind , "Cities": city , "windrose": windrose };

var hash = new L.Hash(Mapknitterunique, allMapLayers);

```

πŸ’Ύ Commit your changes

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

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

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

🏁 Done Ask in comments for a review and also add a screenshot of the address bar of browser showing URL :)

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!

Part of #510 :)

85 Wide selectors in the selector playground can cause GUI overflow issues

Find it on GitHub

Current behavior:

Very long selectors in the selector playground text input box can overflow other page elements: ![image](https://user-images.githubusercontent.com/5534029/57643927-e3d68680-7588-11e9-89fc-9e7c9eb4f2af.png)

Desired behavior:

When some maximum width of the field is reached (based on the browser's width), the user has to scroll to see the rest of the input. Something like this: https://codepen.io/Momciloo/pen/bpyMbB

Steps to reproduce: (app code and test code)

Type or paste a very long selector in to the selector playground text input box. And yes, I know that using selectors that look like this is not recommended :)

Versions

Cypress 3.2, Windows 10, Chrome

86 Fix recent contributors list's logic and repository fetching precedence

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.js, community-toolbox.js, getAllContribsUtility.js and getRecentCommitsUtility.js in the community-toolbox 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:

CHANGES TO BE DONE

  • /models/index.js

diff $DIFF + require('../../node_modules/urlhash/urlHash'); + let org = urlHash().getUrlHashParameter('o') || 'publiclab'; + let getReposUtil = require('../utils/getAllContribsUtility') - window.addEventListener('DOMContentLoaded', initialize()); + window.addEventListener('DOMContentLoaded', () => { + getReposUtil.getAllRepos(org); + initialize(); + });

  • /scripts/community-toolbox.js, at this line

diff $DIFF - model_utils.getItem('repos').then((repos) => { + return model_utils.getItem('repos').then((repos) => {

  • /utils/getAllContribsUtility.js

diff $DIFF + let model_utils = require('../models/utils')

  • /utils/getRecentCommitsUtility.js

diff $DIFF - model_utils.getItem('repos').then((repos) => { + return model_utils.getItem('repos').then((repos) => {

  • [ ] πŸ’Ύ 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!

87 add a personality match plugin

Find it on GitHub

.match john adam

return example

good match but beware

try ways to make it more intelligent, rather than relying on pure randomness

take your time but make something cool, as always, if you need help, join us on discord!

88 Setting up a Twitter application is a lengthy process for new users

Find it on GitHub

When setting up Twitter as a data source our first step that we advise users do is to 'Create a new Twitter application'

Recently Twitter has added a lengthy process to be approved for a twitter application and we could offer new users some more advice as to how to get approved and what Twitter needs to approve.

Links to Twitters application documentation would be useful for users. https://developer.twitter.com/en/apps/create

You also must have a twitter account in order to set up an application and even view the docs.

Is your feature request related to a problem? Please describe. Users would be frustrated if they needed to set up twitter feeds into platform within a short period of time. Especially if they are not familiar with this kind of set up.

Describe the solution you'd like A short description on what a twitter application requires e.g. An existing or new Twitter account preferably linked to your project or organisation, a short description of what kind of twitter information you will gather and what you will do with it,

A short text that reads ' Twitter applications may take a few hours or a few days to be approved by Twitter. Please be aware of this if you need this data quickly'

To reproduce/see this section

To Reproduce Steps to reproduce the behavior: 1. Go to a deployment you have admin access to 2. Log in as 'an admin' 3. Click on 'settings' 4. Scroll down to 'data sources' 5. Choose 'Twitter' You will see the "Create new twitter application" section/link.

Task: Adding new descriptions to solve this ticket

  1. In the text that says 'Create a new twitter application" add "Twitter applications may take a few hours or a few days to be approved by Twitter. Please be aware of this if you need this data quickly." (note: please feel free to improve on this!) -> this section can be added to the en.json key "introstep1_desc" in app/common/locales/en.json within the platform-client repo.

Working on this issue

  • The repository for this change is https://github.com/ushahidi/platform-client. Start here https://docs.ushahidi.com/platform-developer-documentation/getting-started if you have not set up the Ushahidi client before. Notice that you only need to install the platform-client (no need to set up the API for this) as long as you connect it to a live ushahidi.io or Ushahidi testing deployment.

Implementation notes

  • Fix in https://github.com/ushahidi/platform-client repo
  • Hint :bulb: The code handling users can be found here: https://github.com/ushahidi/platform-client/tree/develop/app/settings/users

  • When you are done, πŸ”€ 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.

  • 🏁 When done Ask in comments for a review :)

Want to work on 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!

Ping @rowasc if you need help with this issue!

89 Data sources - "tweets" is always used to describe the content for the "Import to survey" field

Find it on GitHub

Describe the bug When setting up data sources, the data source type is hardcoded and is always "tweets" instead of the correct data source type.

Where was the bug observed Personal test deployment: https://lgbthistoryswuk.ushahidi.io/views/map

To Reproduce Steps to reproduce the behavior: 1. Go to a deployment you have admin access to 2. Log in as 'an admin' 3. Click on 'settings' 4. Scroll down to 'data sources' 5. Choose 'email', or any of the SMS data sources 6. Toggle on 'Accept survey submissions from this source' 7. Toggle on 'Import to survey' 8. In the text that says 'Choose what should be assigned to each survey field Each of the survey's fields are listed below. Choose the data from your tweets that you'd like to use to populate each of those fields.'

Expected behavior The data source type shown in the description should match the one the user is looking at. It should read - For the Twitter data source: Each of the survey's fields are listed below. Choose the data from Twitter that you'd like to use to populate each of those fields.' - For the Email data source: Each of the survey's fields are listed below. Choose the data from Email that you'd like to use to populate each of those fields.' .. etc ...

Is there a workaround? What is it. No

Screenshots

URL / Environment where this happened Any ushahidi.io or testing environment with Ushahidi V3 or V4

Desktop Hardware Details (please complete the following information): - Applies to any OS - Applies to any browser

Working on this issue

  • The repository for this change is https://github.com/ushahidi/platform-client. Start here https://docs.ushahidi.com/platform-developer-documentation/getting-started if you have not set up the Ushahidi client before. Notice that you only need to install the platform-client (no need to set up the API for this) as long as you connect it to a live ushahidi.io or Ushahidi testing deployment.

Implementation notes

  • Fix in https://github.com/ushahidi/platform-client repo
  • Hint :bulb: The file with all the language keys can be found here: https://github.com/ushahidi/platform-client/tree/develop/app/common/locales/en.json
  • When you are done, πŸ”€ 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.

  • 🏁 When done Ask in comments for a review :)

Changes required (first timers only)

  • in the en.json file, look for the key "choosesurveyfielddesc" and replace its value with ``` "Each of the survey's fields are listed below. Choose the data from {{datasourcetype}} that you'd like to use to populate each of those fields.", ```
  • in the datasources.html file, look for the p with the translation key "survey.choosesurveyfield_desc" and replace that

    with

<p translate-values="{datasource_type: provider.name}" translate="survey.choose_survey_field_desc">Each of the survey's fields are listed below. Choose the data from your tweets that you'd like to use to populate each of those fields.</p>

Ping @rowasc if you need help with this issue!

90 Add a fork ribbon

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 files

  • [ ] πŸ’Ύ 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!

91 Add a meta description

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: This is a quick one, but important for the site's SEO at the same time. Based off the docs here you need to add a meta description to the html files. That's it!

  • [ ] πŸ’Ύ 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!

92 Implement legible font size for different media queries

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: Lighthouse indicates that 54.36% of the font right now is too small to read, making users pinch to zoom. To complete this PR, we advise you to read about Legible Font Sizes and accordingly correct the font sizes for different media queries as the one below.

https://github.com/publiclab/inline-markdown-editor/blob/c6342531174ee9dd92538ae63efc1e303cc7e842/dist/inlineMarkdownEditor.css#L46-L49

  • [ ] πŸ’Ύ 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!

93 Redesign `examples/*html`

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: To complete this PR, you need to redesign the index.html and select.html files in order to provide a more engaging and vivid demo to the new comers. What you implement mostly depends on your own acumen, with the essential points that,

    • Subexamples provided in the html files should cover all cases, i.e., the different manipulations that ime has to offer.
    • Theme must match the colours used over at https://publiclab.org, i.e., a contrasting combination of black and white (invert maybe?)
    • You can read about color contrasts, text styling and other best practices here to get you started.
  • [ ] πŸ’Ύ 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!

94 Fix `examples/*html` in `gh-pages` branch to show a working demo

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: Currently, our gh-pages demo doesn't update values. To complete this PR, you need to update replaceUrl fields in our examples/*html of the gh-pages branch (and NOT the main) to http://httpbin.org/post as it returns a 200 back on every POST sent to it (see cURL). We'd also appreciate if you could rope in a few lines from the README.md here on how to create a simple docker env to use httpbin on you local port.

  • [ ] πŸ’Ύ 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!

95 Update CI Node versions

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: To complete this PR, you need to remove node versions 4 and 6 from the .travis.yml file below, and add node version 10. Also, we'd like if you could add a simple "note" subsection to the README.md that shows the basic commands and workflow of the node version manager in order for a contributor to setup and switch between different node versions on their local. You should mention about basic commands such as nvm exec and nvm ls to quickly switch and list all the installed versions, etc. Refer here for help.

https://github.com/publiclab/inline-markdown-editor/blob/c6342531174ee9dd92538ae63efc1e303cc7e842/.travis.yml#L2-L5

  • [ ] πŸ’Ύ 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 Add an installation section

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: To complete this PR, you need to add an installation section in the README.md file that clearly depicts and covers basic steps needed for a first-timer to setup the lib, much of which can be scooped out from the "contributing" section, but should also include any personal steps you think should be mention-worthy which you might have encountered during the process. We expect you to have atleast setup the development environment once on your local machine before attempting this issue.

  • [ ] πŸ’Ύ 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!

97 Remove Bower support

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: To complete this PR, you need to,

    • Remove bower.json
    • Add the same file and bower_components to .gitignore
  • [ ] πŸ’Ύ 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!

98 add search pydocs plugin

Find it on GitHub

99 Cypress commands (e.g. cy.get) return undefined if previous test step fails

Find it on GitHub

Current behavior:

Cypress test runner fails in after() block with error:

``` CypressError: cy.first() failed because it requires a DOM element.

The subject received was:

undefined

The previous command that ran was:

cy.get()

Because this error occurred during a 'after all' hook we are skipping the remaining tests in the current suite: ```

This happens each time a test step fails. In this case, it happens when the following assertion fails js .get('div.header__dob').should('contain', `${patient.birth_date}`)

Desired behavior:

Cleanup step should execute with Cypress commands returning values instead of undefined

Steps to reproduce: (app code and test code)

  1. Write test with before, test & after steps
  2. Have an assertion fail during testing
  3. cy.get should return undefined in after step

Versions

Cypress: 3.2.0 OS: MacOS 10.14.4 Browser: Electron59 & Chrome73

100 Fix Dropdown Width

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.

TODO: Fix the dropdown width which is not responsive ![img](https://user-images.githubusercontent.com/47988669/56815750-12760280-6810-11e9-9c87-c67b128bbe39.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!

  • [ ] πŸ“ Update the file examples/demo.css in the image-sequencer 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

@@ -103,7 +103,7 @@ body > .container-fluid { }

#add-step-btn{ - margin-left: 10px; + width: 100%; }

#addStep .labels { @@ -271,4 +271,8 @@ a.name-header{ margin-bottom:0px; align:center; width:100%; -} \ No newline at end of file +} + +.selectize-input { + width: 100% !important; +}

`` - [ ] πŸ“ **Update** the file [examples/index.html](https://github.com/publiclab/image-sequencer/blob/main/examples/index.html) in theimage-sequencer` repository (press the little pen Icon) and edit the line as shown below.

```diff

@@ -140,14 +140,14 @@ -

+

@@ -141,16 +143,16 @@

-
+

@@ -143,18 +143,18 @@ -

@@ -148,16, +148,16 @@

-
+

```

  • [ ] πŸ’Ύ 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!