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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No vetos yet, and only for collections (not creation).
Also removes Bourbon and Neat in favor of plain Sass.
closes #20
utACK
Btw, you guys can test this by simply running
npm i && npm start(with local IPFS daemon running). That will show data from Rinkeby.@@ -12,26 +14,44 @@ export default Controller.extend({contributorsSorting: Object.freeze(['balance:desc']),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.
do we actually need to await this here?
currentBlock is not used in this function it seems?
We don't want to set it to a promise I think.
@@ -12,26 +14,44 @@ export default Controller.extend({contributorsSorting: Object.freeze(['balance:desc']),Aw crap, of course. Brain fart.
@@ -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",👍
ok, I thought we want to set a promise that ember automatically resolves... like
getContributionsetc. return promises.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.
That's different.
getContributionsdoesn't set a property directly. Wherever it's used, the promise is actually handled.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.(That is to say the model hooks are promise-aware)