machankura/mempool
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix pool component hashrate api response handling

Browse Source
This commit is contained in:
nymkappa 2022-04-23 15:50:45 +09:00
parent 6ae20ead63
commit 0803fed0f4
No known key found for this signature in database
GPG Key ID: E155910B16E8BD04
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
backend/src/repositories/HashratesRepository.ts
View File

@ -102,7 +102,7 @@ class HashratesRepository {
/** /**
* Returns a pool hashrate history * Returns a pool hashrate history
*/ */
public async $getPoolWeeklyHashrate(slug: string): Promise<any[]> { public async $getPoolWeeklyHashrate(slug: string): Promise<any[]> {
const pool = await PoolsRepository.$getPool(slug); const pool = await PoolsRepository.$getPool(slug);
if (!pool) { if (!pool) {
throw new Error(`This mining pool does not exist`); throw new Error(`This mining pool does not exist`);

2
frontend/src/app/components/pool/pool.component.ts
View File

@ -56,7 +56,7 @@ export class PoolComponent implements OnInit {
.pipe( .pipe(
switchMap((data) => { switchMap((data) => {
this.isLoading = false; this.isLoading = false;
this.prepareChartOptions(data.hashrates.map(val => [val.timestamp * 1000, val.avgHashrate])); this.prepareChartOptions(data.map(val => [val.timestamp * 1000, val.avgHashrate]));
return [slug]; return [slug];
}), }),
); );