Closed shekohex closed 1 year ago
For the config files I would also write a test case which goes through all of them and attempts to parse them. If a config file fails to parse, the test fails and we notice that there is something wrong with the given config file. That way we can easily avoid broken config files. I can implement that if it sounds good.
For the config files I would also write a test case which goes through all of them and attempts to parse them. If a config file fails to parse, the test fails and we notice that there is something wrong with the given config file. That way we can easily avoid broken config files. I can implement that if it sounds good.
I like the Idea, I will add a small sub-command to the relayer CLI to does this for us.
I dont think that requires a cli command, a simple #[test]
function which walks through files in the config folder should be enough.
CI is falling, needs #371 to be merged first and then will update my PR here.
Summary of changes
example/config.toml
file for quick startReference issue to close (if applicable)
Code Checklist