When compiling release binaries, a file containing all checksums is automatically generated. It's possible to manually parse that file using splitting, trimming and combining strings. But would't it be much nicer if, next to the checksum.txt, there's also a artifacts.json(or something like that) that contains information about the artifacts? Many libraries exist to parse JSON strings so that information could be extracted more easily for different use cases.
When compiling release binaries, a file containing all checksums is automatically generated. It's possible to manually parse that file using splitting, trimming and combining strings. But would't it be much nicer if, next to the
checksum.txt
, there's also aartifacts.json
(or something like that) that contains information about the artifacts? Many libraries exist to parse JSON strings so that information could be extracted more easily for different use cases.Example: