Allowing extra spaces on the TARGET environment variable
The value is hard to read, and being able to column-align it with the tokens makes it easier to scan if one is configuring it correctly and avoid mistakes, in case one plans to keep more than one of these to non-zero values.
This commit is contained in:
parent
2ff7dbaf62
commit
3e58974b41
|
@ -57,8 +57,13 @@ if (!groupIds) {
|
|||
throw new Error(`Group ${groupName} not found`);
|
||||
}
|
||||
|
||||
// Target values to keep in spot, ordered the same as in mango client's ids.json
|
||||
// Example:
|
||||
//
|
||||
// MNGO BTC ETH SOL USDT SRM RAY COPE FTT MSOL
|
||||
// TARGETS=0 0 0 1 0 0 0 0 0 0
|
||||
const TARGETS = process.env.TARGETS
|
||||
? process.env.TARGETS.split(' ').map((s) => parseFloat(s))
|
||||
? process.env.TARGETS.replace(/\s+/g,' ').trim().split(' ').map((s) => parseFloat(s))
|
||||
: [0, 0, 0, 0, 0, 0, 0, 0, 0];
|
||||
|
||||
const mangoProgramId = groupIds.mangoProgramId;
|
||||
|
|
Loading…
Reference in New Issue