Closed schemar closed 5 years ago
Ready for review 🦑
- Should
MosaicCoreConfig
be updated?
I don't understand. Can you please elaborate?
- Should the range script end with the first value to have failing tests (current behavior) or handle failing tests with each value in the range?
I will change the script to run all the tests and change the exit code based on whether a test fails.
- Should
MosaicCoreConfig
be updated?I don't understand. Can you please elaborate?
@schemar: apologies for not being specific. From MosaicCoreConfig
:
/** The number of decimals of the base token. */
uint256 public constant DECIMALSFACTOR = 10 ** uint256(18);
I asked because of the changes to base token references in this PR. On the other hand, perhaps those references shouldn't be dynamic and should always have 18 decimals?
- Should
MosaicCoreConfig
be updated?I don't understand. Can you please elaborate?
@schemar: apologies for not being specific. From
MosaicCoreConfig
:/** The number of decimals of the base token. */ uint256 public constant DECIMALSFACTOR = 10 ** uint256(18);
I asked because of the changes to base token references in this PR. On the other hand, perhaps those references shouldn't be dynamic and should always have 18 decimals?
Hm 🤔 Good point. Mosaic core is way outdated by now. It's probably not worth it to mingle around in the core code in the context of this PR.
Ready for review again. Now accepts one and two arguments and continues after failed decimal (prints all failed decimals at the end).
env
override).MockToken
to take decimals as constructor argument.test:range
. Example:npm run test:range -- 16 18
Fixes #735