Giter Club home page Giter Club logo

platform's People

Contributors

akhilcryptos avatar alpa-coder avatar berkes avatar ccallergard avatar james-allein avatar karelstriegel avatar marc0olo avatar qkyrie avatar rsercano avatar simsteve7 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

platform's Issues

When clicking "cancel" in the civic modal dialog, the user gets logged in anyway

Expected behavior

When clicking "cancel" in the civic modal dialog, I would expect that log in would fail

Actual behavior

When clicking "cancel" in the civic modal dialog, the user gets logged in anyway

Probably this is due to the fact that I'm still logged in, and I can not log out.
So, maybe first fix the log out...and then test this issue after logging out

Steps to reproduce the behavior

Click "cancel" in the civic modal dialog
screen shot 2017-11-07 at 23 15 47

As a FundRequestUser, I consult an overview of my FundRequestIssues (funded/solved)

  1. User is logged in (with his primary account: Gmail / Outlook)
  2. User clicks on menu-item "Requests"
  3. User sees an overview of all FundRequestIssues (unfunded/funded)
  4. (optional) As a (Solver)FundRequestUser, I can link a GitHub-account to my primary account, so that I can consult my solved FundRequestIssues for which I can claim the reward
    4.1. User clicks on the "Connect to GitHub"-button
    4.2. The FundRequestPlatform opens a modal dialog where the User can link his primary account
    to his GitHub-Account
    4.3. The FundRequestPlatform retrieves the GitHub-Account which is linked to the
    User.PrimaryAccount
    4.4. The FundRequestPlatform retrieves all the funded FundRequestIssues which are solved by
    the User.PrimaryAccount.GitHubAccount from GitHub (see also #19)
    4.5. The overview is reloaded, and for each FundRequestIssue which is solved by his linked
    GitHub-account, a "Claim Reward"-button is added

Overview of unfunded/funded FundRequestIssues + "Connect to GitHub"-button
consult overview of unfunded and funded fundrequestissues

Modal Dialog where the User can link his primary account to his GitHub-Account
consult solved fundrequestissues modal dialog to link githubaccount copy simple

Overview of unfunded/funded FundRequestIssues AND solved FundRequestIssues with "Claim Reward"-button + "Connected to GitHub"-info
consult solved fundrequestissues copy

As a (solver)FundRequestUser, I can link a RepositoryAccount to my primary account which I used to log in

  1. User is logged in (with his primary account: Gmail / Outlook)
  2. User clicks on the top-left user account icon (cfr. Hello, <-username->)
  3. User consults the detailed overview screen of his primary account which was used to log in to the FR-platform
  4. User clicks on the "Link Account" button
  5. A modal dialogue is opened where the user can fill in the username/password of the RepositoryAccount to be linked
  • A) IF GitHub-Account (login+password) exists, THEN the GitHub-Account is linked to the primary account, and user returns to the detailed overview page of the primary account

  • B) IF GitHub-Account (login+password) doesn't exist, THEN error-message to the user + user returns to the modal dialogue so that he can update the GitHub-Account details (login+password) or can cancel the link-operation

consult primary account details page

link githubaccount to primary useraccount

As a (Solver)FundRequestUser, I can consult an overview of my solved FundRequestIssues

  1. User is logged in (with his primary account: Gmail / Outlook)
  2. User clicks on menu-item "Solved Requests"
    2.A IF User.PrimaryAccount is not linked to a GitHub-account, THEN a modal dialog is opened where the User can link his primary account to his GitHub-Account
  3. The FundRequestPlatform retrieves the GitHub-Account which is linked to the User.PrimaryAccount
  4. The FundRequestPlatform retrieves all the funded FundRequestIssues which are solved by the User.PrimaryAccount.GitHubAccount from GitHub (see also #19)
  5. User consults the overview screen of the funded FundRequestIssues which are solved by his linked GitHub-account

consult solved fundrequestissues modal dialog to link githubaccount

consult solved fundrequestissues

As a (Solver)FundRequestUser, I can claim the reward of a funded FundRequestIssue solved by me

Pre-requisite

  1. User is logged in (with his primary account: Gmail / Outlook)
  2. A GitHub-account is linked to my primary account. see flow of #22

consult solved fundrequestissues copy

Normal flow
1: The FundRequestUser chooses to claim the reward/funds from a funded FundRequestIssue, and clicks the "Claim Reward"-button
2: The FundRequestPlatform checks with the RepositoryPlatform if the FundRequestIssue.RepositoryIssue is solved by the current (Solver)FundRequestUser
IF Yes, Then:
3: The FundRequestPlatform asks for the (Solver) FundRequestUser.ethereumAddress
4: the (Solver) FundRequestUser confirms his ethereumAddress
5: The FundRequestPlatform send the transaction to the FundRequestContract
5. The FundRequestPlatform calls the FundRequestUser's Wallet to open it for the rewarding-transaction
6. The FundRequestUser confirms the rewarding-transaction to the FundRequestUser's Wallet
7. The FundRequestUser's Wallet submits the rewarding-transaction to the FundRequestContract
8. The FundRequestUser's Wallet informs the FundRequestPlatform that the rewarding-transaction is submitted to the FundRequestContract
9. The FundRequestPlatform informs the FundRequestUser about the updated state
10. FundRequestUser is informed about updated intermediate state = "Rewarding transaction pending"
11. The rewarding-transaction is mined on the Ethereum Blockchain
12. The rewarding-transaction is registered as an FundRequestContractEntry in the FundRequestContract
13. The FundRequestContract sends a notification to the FundRequestPlatform
14. The FundRequestPlatform informs the FundRequestUser about the updated state
15. FundRequestUser is informed about updated final state = "Rewarding transaction successful"

claim button clicked

claim button clicked2

claim button clicked3

Make MVP mobile friendly

Menu automatically collapses

Only viewing of FundRequestIssue's

Disable funding

Responsive table for issue's

  • columns that can be left out: Type, Technologies, Actions

It is possible to approve 0 FND's (and this transaction consumes gas)

Expected behavior

It should only be possible to approve strictly more than 0 FND's

Note: probably this is expected behaviour, but this is not clear to a new user...maybe the naming of the approved should be different...something as "Wallet: approved saldo" (?)
And then the "approve"-modal view, can also be changed into "update wallet's approved saldo"

TODO1:
label "Approved for use: 0.00 FND" --> "Approved saldo"
button label "Approve FND's" --> "Update saldo"

TODO2:
titel of model dialog: "Approve FND's" --> "Update saldo"
label in model dialog: "Approve Amount" --> "Update approved saldo to:"

Actual behavior

It is possible to approve 0 FND's --> this consumes gas :(

Steps to reproduce the behavior

See screenshots

screen shot 2017-12-04 at 23 09 16

screen shot 2017-12-04 at 23 09 26

screen shot 2017-12-04 at 23 09 36

screen shot 2017-12-04 at 23 10 40

When adding a new FundRequestIssue which already exists, the user is not guided to the correct issue

Expected behavior

User is guided to the (existing) issue he wanted to add (number 12 in this testcase)

Actual behavior

User is not guided to the (existing) issue he wanted to add (number 4 instead of number 12 for this testcase)

Steps to reproduce the behavior

see screenshots

  • Add an existing Github-FundRequestIssue: e.g. FundRequest/area51#12

  • Click "Go to request" --> this links to issue number 4, instead of expected number 12

screen shot 2017-12-04 at 22 29 53

screen shot 2017-12-04 at 22 30 06

Log out doesn't work

Expected behavior

User is logged out and guided to the welcome-page/login-page. Or a dedicated logout-page

Actual behavior

After clicking logout button
screen shot 2017-11-07 at 23 32 22

Steps to reproduce the behavior

Click on the logout button (=> in the right top corner)
screen shot 2017-11-07 at 23 23 35

Balance shown as NaN

Expected behavior

Shows correct balance

Actual behavior

Shows NaN as balance

Steps to reproduce the behavior

  • go to webapp
  • login
  • view NaN

image

Activity stream is not working

Only a box is shown...so, if no activity, do not show the activity box
In case of activity, this box is shown with activities

screen shot 2017-11-07 at 23 45 39

Display version in the frontend of the platform

Expected behavior

For each build/deploy the frontend should display the version of the code

Could be added after or before the copyright
image

Idealy it would also act as a link to our github platform repository and if possible link it to either a tag or to a commit hash.

Actual behavior

Currently the version is not visisble

Steps to reproduce the behavior

Just surf to the platform application

Status is not correctly updated from OPEN --> FUNDED

Status is not correctly updated from OPEN --> FUNDED

Funded a new Request, but status didn't change from OPEN --> FUNDED

Probably the statistics are also not correct then because based upon these statusses...to be checked?!

screen shot 2017-11-08 at 00 19 00

Problems 06/11/2017

  • Unable to start a request
  • Search bar disappeared
  • logout doesn't work (still pointing to old auth mec.)
  • Logo looks messed up

Funding Expiration Date

When I fund an issue, the value of this issue being resolved for me diminishes over time. I would like to know that my fund will be released back to me after a specific period of time.
When I fund an issue, I would like to enter the expiration date of my fund along with the FND amount

Using Google login, the name with non-ascii chars is not shown correctly

Expected behavior

Show my name correctly below the profile image

Actual behavior

name is shown with ? chars instead of ü (and the like)

Steps to reproduce the behavior

  • add non-ascii chars to your name in your google profile
  • login to fundrequest with google
  • look at your profile in the top left corner

bildschirmfoto vom 2017-10-12 12-04-09

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.