Open iamchrissmith opened 4 years ago
One thing as I dig into this @ehildenb that might make it easier. The randont-test.out
file has:
### Solidity
------------
Starting the Solidity, but it does not have a similar closing comment so maybe we have a
### End Solidity
tag so we can more easily grab the solidity.
also what would be the best identifier for each test. From this:
Running: krun --directory .build/defn/llvm /var/folders/bq/n6l0m1pj3s94hpl85c576d9r0000gn/T/tmpimullwdh --term --no-sort-collections --output json --parser cat
I would think it is the last piece: tmpimullwdh
If that is the case, would it be too difficult to put that in the solidity starting tag, something like:
### Solidity
#### ID: tmpimullwdh
------------
this PR addresses the solidity end block and the ID: https://github.com/makerdao/mkr-mcd-spec/pull/161
@ehildenb @iamchrissmith we will need to do some variable name changes in the export file, as some capitalised variables enter in conflict with the contract names. If we can also do some other changes will suit better with the deployer base contract we have already implemented reducing the amount of custom code for this repo.
Mandatory:
Vat
=> vat
Vow
=> vow
Cat
=> cat
Pot
=> pot
Flap
=> flap
Flop
=> flop
End
=> end
Spot
=> spotter
(not showed in this example but just in case in some other test is there)
Desired for consistency:
Alice
=> alice
Bobby
=> bobby
ADMIN
=> admin
ANYONE
=> anyone
Flip_gold
=> goldFlip
GemJoin_gold
=> goldJoin
I'll see if I find some other cases we need changes.
@gbalabasquer I created this PR to start to address these: https://github.com/makerdao/mkr-mcd-spec/pull/163
Let me know what you think
I thought it would be good to have a place where we capture the Solidity output conversation outside the meeting notes issue. Current output notes:
ACTIONS
Originally posted by @ehildenb in https://github.com/makerdao/mkr-mcd-spec/issues/22#issuecomment-584471391