Switch to contribution token instead of proposals #100

Merged
raucao merged 5 commits from feature/20-contributions into master 2019-04-09 20:25:36 +00:00
raucao commented 2019-04-09 10:57:32 +00:00 (Migrated from github.com)

No vetos yet, and only for collections (not creation).

Also removes Bourbon and Neat in favor of plain Sass.

closes #20

No vetos yet, and only for collections (not creation). Also removes Bourbon and Neat in favor of plain Sass. closes #20
bumi commented 2019-04-09 14:21:39 +00:00 (Migrated from github.com)

utACK

utACK
raucao commented 2019-04-09 15:18:37 +00:00 (Migrated from github.com)

Btw, you guys can test this by simply running npm i && npm start (with local IPFS daemon running). That will show data from Rinkeby.

Btw, you guys can test this by simply running `npm i && npm start` (with local IPFS daemon running). That will show data from Rinkeby.
bumi (Migrated from github.com) requested changes 2019-04-09 20:06:07 +00:00
@@ -12,26 +14,44 @@ export default Controller.extend({
contributorsSorting: Object.freeze(['balance:desc']),
bumi (Migrated from github.com) commented 2019-04-09 20:03:10 +00:00

I think this should be the other way round.
unconfirmed = confirmedAt > currentBlock

or:
if the currentBlock is smaller than the block number in confirmedAt then the contribution is not confirmed.

I think this should be the other way round. unconfirmed = confirmedAt > currentBlock or: if the currentBlock is smaller than the block number in confirmedAt then the contribution is not confirmed.
bumi (Migrated from github.com) commented 2019-04-09 20:03:48 +00:00
      return this.currentBlock >= contribution.confirmedAt;
```suggestion return this.currentBlock >= contribution.confirmedAt; ```
bumi (Migrated from github.com) commented 2019-04-09 20:04:16 +00:00
      return this.currentBlock < contribution.confirmedAt;
```suggestion return this.currentBlock < contribution.confirmedAt; ```
bumi (Migrated from github.com) commented 2019-04-09 20:05:29 +00:00

do we actually need to await this here?
currentBlock is not used in this function it seems?

do we actually need to await this here? currentBlock is not used in this function it seems?
raucao (Migrated from github.com) reviewed 2019-04-09 20:14:04 +00:00
raucao (Migrated from github.com) commented 2019-04-09 20:14:04 +00:00

We don't want to set it to a promise I think.

We don't want to set it to a promise I think.
raucao (Migrated from github.com) reviewed 2019-04-09 20:14:22 +00:00
@@ -12,26 +14,44 @@ export default Controller.extend({
contributorsSorting: Object.freeze(['balance:desc']),
raucao (Migrated from github.com) commented 2019-04-09 20:14:21 +00:00

Aw crap, of course. Brain fart.

Aw crap, of course. Brain fart.
bumi (Migrated from github.com) reviewed 2019-04-09 20:14:59 +00:00
@@ -16,3 +16,3 @@
"start": "ember serve",
"test": "ember test",
"start": "KREDITS_APM_DOMAIN=open.aragonpm.eth ember serve",
"start:local": "WEB3_PROVIDER_URL=http://localhost:7545 ember s",
bumi (Migrated from github.com) commented 2019-04-09 20:14:59 +00:00

👍

:+1:
bumi (Migrated from github.com) reviewed 2019-04-09 20:18:54 +00:00
bumi (Migrated from github.com) commented 2019-04-09 20:18:54 +00:00

ok, I thought we want to set a promise that ember automatically resolves... like getContributions etc. return promises.

ok, I thought we want to set a promise that ember automatically resolves... like `getContributions` etc. return promises.
bumi commented 2019-04-09 20:20:08 +00:00 (Migrated from github.com)

we soon also need to load the balances from the confirmed contributions or add more information on what we show. otherwise it is a bit misleading.

we soon also need to load the balances from the confirmed contributions or add more information on what we show. otherwise it is a bit misleading.
raucao (Migrated from github.com) reviewed 2019-04-09 20:22:00 +00:00
raucao (Migrated from github.com) commented 2019-04-09 20:22:00 +00:00

That's different. getContributions doesn't set a property directly. Wherever it's used, the promise is actually handled.

That's different. `getContributions` doesn't set a property directly. Wherever it's used, the promise is actually handled.
raucao commented 2019-04-09 20:23:27 +00:00 (Migrated from github.com)

we soon also need to load the balances from the confirmed contributions or add more information on what we show. otherwise it is a bit misleading.

Yes, but we currently don't get the correct balance of kredits earned via getContributors. It's a new issue, but I agree that it is the next urgent one.

> we soon also need to load the balances from the confirmed contributions or add more information on what we show. otherwise it is a bit misleading. Yes, but we currently don't get the correct balance of kredits earned via `getContributors`. It's a new issue, but I agree that it is the next urgent one.
bumi (Migrated from github.com) approved these changes 2019-04-09 20:23:56 +00:00
raucao (Migrated from github.com) reviewed 2019-04-09 20:24:42 +00:00
raucao (Migrated from github.com) commented 2019-04-09 20:24:42 +00:00

(That is to say the model hooks are promise-aware)

(That is to say the model hooks are promise-aware)
Sign in to join this conversation.