fix json generation

[MatusKysel]

After recent change in spec, we need to run go generate to get tests.json file used for testing in ssv. But because of runtime.Caller(0) generating json outside the repo is impossible. Whit this proposed change we can run it in any directory, where the binary used for generating code is located

[GalRogozinski]

I think you should use filepath tools
I think they are not system dependent..

I think currently it is possible to work on spec tests from Windows (never tried it)

[MatusKysel]

I think you should use filepath tools I think they are not system dependent..

I think currently it is possible to work on spec tests from Windows (never tried it)

I don't see anything that will not work on windows except permissions. But I am unsure how to fix that

[MatheusFranco99]

@MatusKysel, you've made the change for the qbft and ssv modules, but not for the types one. Is it not tested on your side? I think that, even so, we may adjust it in a similar manner for consistency.

[GalRogozinski]

@MatusKysel
As far as I know windows uses backslashes (\) while macos/linux use forward slashes (/) like you used.
You honestly tackled me on the permission bit, but chatgpt tells me Windows simply ignores the commands.

Anyhow fileutils is there to take care of all cross compatibility issue, and it is considered a programming best practice to always use such libs for files (at least this is what I was taught as a baby dev)

[MatusKysel]

@MatusKysel As far as I know windows uses backslashes () while macos/linux use forward slashes (/) like you used. You honestly tackled me on the permission bit, but chatgpt tells me Windows simply ignores the commands.

Anyhow fileutils is there to take care of all cross compatibility issue, and it is considered a programming best practice to always use such libs for files (at least this is what I was taught as a baby dev)

@GalRogozinski check it one more time, I am actually fixing it

[GalRogozinski]

I know this isn't on you but can you change permissions to everytime we write file to (0664). This should solve issues when we run generate several times