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!
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!
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 MYSQL.md https://github.com/publiclab/mapknitter/blob/main/MYSQL.md
Line no. 195
Change you database to your database
[ ] πΎ 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.
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!
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.
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.
At the top of the README, where you'll find other badges, lets add the following line:
[](https://publiclab.org/chat)
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
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.
[ ] 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 UI: "Found undefined alias for 'myalias'" when multiple aliases defined for element
When using .as('myalias') in a loop the message Found undefined alias for: 'myalias' shows up in the UI but it still works (in the console you can see that the alias resolved to two elements).
The message does not show up when the loop is only executed once.
Desired behavior:
This message should not appear and irritate the developer :)
Steps to reproduce: (app code and test code)
typescript
describe('Test', () => {
it('test', () => {
cy.visit('http://google.com');
for (let i = 0; i < 2; i += 1) {
cy.get('[name="btnK"]').as('search-button');
cy.get('@search-button');
}
});
});
Versions
|||
|-|-|
|Cypress|3.3.1|
|OS| Windows 10|
|Browsers| Electron headed|
PS:
Am I using aliases incorrectly here or is this just a misguided message from the UI?
10 Change colour for the featured tags on /questions page
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 featured tags on https://publiclab.org/questions are not showing up.
Update apps/views/questions/index.html.erb in the plots2 repository.
Add color style to the feature imported in L-12 to L-16
[ ] πΎ 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!
11 Remove redundant function from community-toolbox.js
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:
π¬β° - 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.
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; }'
```
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.
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
17 Collect CI environment variable from Concourse CI
Add environment variables to collect from https://concourse-ci.org/implementing-resource-types.html#resource-metadata
$BUILD_ID
$BUILD_NAME
$BUILD_JOB_NAME
$BUILD_PIPELINE_NAME
$BUILD_TEAM_NAME
$ATC_EXTERNAL_URL
If the build is a one-off, $BUILD_NAME, $BUILD_JOB_NAME, and $BUILD_PIPELINE_NAME will not be set.
I see quite a few other env variables floating around starting with CONCOURSE_, which can probably be used to identify it as a run within Concource CI.
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:
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.
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!
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.cssselectize.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:
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.
π¬β° - 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.
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.
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
ReplaceImage.js add const $ = window.$; at line 4 in ReplaceImage()
Ui.js add const $ = window.$; at line 3 in CropModuleUi()
Crop.js and modify line 20 as
diff
-backgroundColor = options.backgroundColor.split(' ');
+var backgroundColor = options.backgroundColor.split(' ');
```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:
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.
π¬β° - 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.
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!
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:
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.
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!
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:
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.
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
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 :
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!
Very long selectors in the selector playground text input box can overflow other page elements:
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
29 Fix recent contributors list's logic and repository fetching precedence
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!
π¬β° - 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.
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.
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.LatLng to initialize the starting positions of our images corners, but we don't take advantage of their suggested class factory syntax. Let's update the code in the files indicated below.
Solution
Where to find the relevant lines of code:
Remove the new keyword from the following code blocks and update L.LatLng to L.latLng :
[ ] Create a new feature branch with a unique name descriptive to the issue
[ ] Try to fix the issue following the steps above, but even before you're done, you can:
commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
[ ] Reference this issue in your pull request body
[ ] Once you submit your pull request, if there's an additional checklist provided for getting it merged, get those boxes checked off. Either way, mention me @sashadev-sky for a review.
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, 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
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:
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.
π¬β° - 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.
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 match the address bar's color to PublicLab's site, i.e., a #000 black in the steps indicated here
[ ] πΎ 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.
π¬β° - 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.
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, bring about some simple CSS changes so that the site specifies the criteria window.innerWidth === window.outerWidth, for a better accessibility score overall. Please refer here for more details.
[ ] πΎ 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.
π¬β° - 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.
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:
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.
π¬β° - 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.
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.
π¬β° - 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.
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:
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.
π¬β° - 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.
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/*htmlof 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.mdhere 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:
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.
π¬β° - 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.
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.
π¬β° - 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.
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:
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.
π¬β° - 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.
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:
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.
π¬β° - 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.
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: You'll need to delete the bower.json in the root folder and exclude bower_components from .gitignore as well.
[ ] πΎ 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.
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!
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
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
π 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:
#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:
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.
π¬β° - 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.
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, "Public Lab" on the navbar links the user to the rootpath i.e, dashboard. Instead it should link to the https://publiclab.org/home page as we already have a separate dashboard link on the navbar.
Update apps/views/layouts/header.html.erb in the plots2 repository.
Change href="<%= root_path %>" to href="/home" on line 14
[ ] πΎ 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!
Describe the bug
I am not able to delete a wrong annotation in Mac using Chrome.
To Reproduce
Steps to reproduce the behavior:
1. Go to imglab.ml/#. Open an image
2. Click on Polygon. Try to make an annotation. And then try to delete it.
3. It fails
Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
Even after pressing delete key multiple times, it is not working.
Console Errors
<!-- if possible, provide console logs (press F12 to see browser console). -->
None
Device detail
(please complete the following information):
- OS: [e.g. Ubuntu] Mac
- Browser [e.g. chrome, firefox] Chrome
Additional context
<!-- Add any other context about the problem here. -->
Watch for changes, or Bookmark for easy discovery.
Fund this project for new features and maintenance.
[Showcase] your project with us by raising an issue
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!
π 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!
Part of #381
cy.server command has a really useful option onAnyRequest. Which is really practical to inject headers or do other stuff.
Here is blog post describing how it can be used : https://medium.com/agilix/cypress-testing-include-custom-http-header-on-each-http-request-2b3693813e97
This option and apparently a few other ones are not documented and are also not available in the Typescript definition (cli/types/index.d.ts) (so cannot be used when using Typescript).
Desired behavior:
Having at least the Typescript definition updated, and if possible a line in the documentation about this option.
Steps to reproduce: (app code and test code)
js
cy.server({
onAnyRequest: function (route, proxy) {
//...
}
});
This will not work when using typescript, it works with js.
This projects need a website, I would love help on this. Just a website having the information would do (~bumbly/jumbly). This is an easy task if you would like creating the base html(black text on white) code website, writing I will do.
55 Argument parsing crashes badly if passing "spec: {}"
```js
const cypress = require('cypress')
cypress.run({
// this works fine
// spec: 'cypress/integration/spec.js'
// this crashes badly - hanging Cypress
spec: {}
/*
this exits because no specs were found
Can't run because no spec files were found.
We searched for any files matching this glob pattern:
*/
// spec: []
})
```
I have created example in https://github.com/cypress-io/cypress-test-tiny/pull/44
We should document the use of @alias.all and @alias.2 within a couple of documents:
- https://docs.cypress.io/guides/core-concepts/variables-and-aliases.html
- https://docs.cypress.io/api/commands/get.html#Alias
When referencing aliases, you can reference @alias.all or @alias.2 and it will return respectively all of the aliases of that name or the 2nd request matching the name.
Examples:
js
it("does not poll for list again", function() {
cy.wait("@getList");
cy.tick(10000);
// does not poll for another request
cy.get("@getList.all").should("have.length", 1);
});
This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you π