fundrequest / chrome-browser-plugin Goto Github PK

Context

Chrome browser plugins have to be installed from the chrome web store. The goal of this story is to make the FundRequest-Github browserplugin available on the chrome web store.

Flow of events

1. The user navigates to the chrome web store.
2. The user searches for the FundRequest-Github browserplugin.
3. The user installs the FundRequest-Github browserplugin.
4. The user opens the FundRequest-Github browserplugin.
5. The user sees the funding on Github issues when using the FundRequest-Github browserplugin.

Testcases

• Testcase: A user has installed the FundRequest-Github browserplugin. The user surfs on Github and there are funded issues displayed.
  -- Result: The user sees the funding on issues.

At the moment it seems that the chrome ext. can't handle other ERC20 tokens

Issue funded with XUC

Issue funded in FND

For example check the URL: Area51-Milestone1

In this overview, there's no .issue-meta-section which broke the code and it's impossible to show funds even if we implement this

As a user I would like to receive notifications in the chrome extension

Doesn't load anymore

on

Context

When developers are working on Github it is interesting for them to see the funding on issues so they are more likely to start an issue that is funded. We already implemented to see the funding of an issue on an overview of issues when a user has our browser plugin installed. The goal of this story is to also display the funding on the detail page of an issue.

Prerequisites

The user has to use the chrome browser.
The user has to have installed the FundRequest - GitHub plugin.

Flow of events

1. The user navigates to GitHub.
2. The user opens the overview of issues of a GitHub project.
3. The user sees the issues of the project and for the funded issues the amount and the currency of the funding.
4. The user opens the detail page of an issue.
5. The user sees the funding for the specific issue he opened.

Testcases

• Testcase: A user has installed the FundRequest - Github plugin and opens an issues of a project on Github. The issue is funded on FundRequest.
  • Result: The amount of funding is displayed on the details page of the issue.
• Testcase: A user has installed the FundRequest - Github plugin and opens an issues of a project on Github. The issue is funded on FundRequest.
  • Result: There is no amount of funding displayed on the details page of the issue.

need for:

• tokenContractAddress
• frContractAddress

Context

In previous stories we already added the functionality to use a Chrome browser plugin to view the funding on Github issues. The goal of this story is to make it possible to fund an issue from within the plugin as well.

Prerequisites

• The user has installed the FundRequest browser plugin for Github.
• The user has installed the Metamask plugin.

Flow of events

1. The funder navigates to the detail page of a Github issue.
2. The funder chooses to fund the issue.
3. A new tab is opened an goes to the wizard ready to fund the request. As much detail as possible is prefilled in into the wizard

Migration is done, newest FundRequestContract for Test environment = 0x55356bccfa48d09dc824c0aea6ebd868ff5edf50

Please also remove the development env and add the testing env (tst1) to the browser extention available envs

It seems that the browser extension only targets the following url syntax:
https://github.com/ORG/REPO/issues?....

Some variations in the url are ignored. Some examples
https://github.com/FundRequest/platform/labels/Community

Issue FundRequest/platform#441 is funded, and that is also visible in the issue overview.

But when adding the label filter the plugin stops displaying the funded information in the filtered issue overview

In the settings of the github plugin, you can choose the network.

The dropdown is not correct and does not apply the correct settings. Rename in the settings 'network' to 'Environment'
It should be:

• Production (Mainnet): https://fundrequest.io
• Staging (Kovan): https://staging.fundrequest.io
• Development (Kovan): https://dev-web.fundrequest.io
• Local (Kovan): http://localhost:8080

Production should be the default

The extension should follow the webextension standard and also work on Firefox

Context

At the moment funding is only possible in the FND token. In the FundRequest platform contract it is possible to specify another ERC-20 token that is allowed to fund issues in a certain repository. The front end should support this by:

• displaying the funding in multiple ERC-20 tokens;
• allowing to fund in other ERC-20 tokens as FND when adding funding to an issue.

Flow of events

1. The funder chooses to add funds to an issue on a repository that allows funding in another token as FND.
2. The Github browser plugin displays the funding dialog with the option to choose the token to be used.
3. The user chooses which token he want to use.
4. The user adds te funding to the issue.
5. When the transaction is processed the funding is displayed on the issue. In case of funding in multiple tokens the funding in the different tokens is diplayed.

Additional info

• FND is the default choice to add funding
• It is possible that an issue is funded in FND and the repository's native token. Both have to be displayed on the overview screen of issues and the detail screen of issues.

Testcases

• Testcase: The user wants to fund an issue on a repository that only allows funding in FND.
  • When the user chooses to fund he cannot choose the currency to fund in.
• Testcase: The user wants to fund an issue on a repository that allows funding in FND and the native token of the project of the repository.
  • When the user chooses to fund he cannot choose between FND and the project's token to fund.
• Testcase: An issue is funded in one currency.
  • On the overview screen and detail screen the funding in the one currency is displayed.
• Testcase: An issue is funded in multiple currencies.
  • On the overview screen and detail screen the funding in both currencies is displayed.

By following the current install guide a developer is unable to build the extension.
We should also define npm/node versions, seen that the "current" version is a moving target.

The bug is in
https://github.com/FundRequest/chrome-browser-plugin/blob/aeebd5de7cf15e2501a104dcd124b02d4964ccbc/src/classes/models/RequestFunds.ts

Here, funds.fndFunds will be null when only funded with 'other' token

Display all values that are shown in the browser plugin in USD.

When going back and forward to a github issue, the fundrequest information is added each time

There are some permissions required that shouldn't be necessary for the plugin.

Should def. be removed:

• Manage your apps, extensions, and themes
• Read your browsing history

To check:

• Change your settings that control websites' access to features such as cookies, JavaScript, plug-ins, geo-location, microphone, camera etc.

• Only funded issues should have the added section in the general overview.
• Please add the fundrequest icon in the issue overview, to make it easier to scan for funded
  issues.
• Update the default separator (see design image below)
• Display total funding in USD

Context

When developers are working on Github it is interesting for them to see the funding on the different issues so they are more likely to start an issue that is funded.

Prerequisites

The user has to use the chrome browser.
The user has to have installed the FundRequest - GitHub plugin.

Flow of events

1. The user navigates to GitHub.
2. The user opens the overview of issues of a GitHub project.
3. The user sees the issues of the project and for the funded issues the amount and the currency of the funding.

Testcases

• Testcase: A user has installed the FundRequest - Github plugin and opens the overview of issues of a project on Github. There is an issue that is funded on FundRequest.
  • Result: The amount of funding is displayed in the list with the other information on the issue.
• Testcase: A user has installed the FundRequest - Github plugin and opens the overview of issues of a project on Github. There is an issue that is not funded on FundRequest.
  • Result: There is no amount of funding displayed in the list for this issue.

Context

In previous stories we already added the functionality to use a Chrome browser plugin to view and fund Github issues. The goal of this story is to make it possible to claim the funds of an issue from within the plugin as well.

Prerequisites

The user has installed the FundRequest browser plugin for Github.
The user is logged into GitHub

Flow of events

The claimer navigates to the detail page of a Github issue.
The claimer sees a claim button
The claimer can press the claim button and a new tab opens with the request detail on fundrequest where he is able to handle the claim.