Let's consider the ways of automation of the spec validation

[akhundMurad]

TypeID now has a lot of implementations in different programming languages. Therefore, there should be a way of tracking their validation statuses (against spec). I am wondering about a badge, that can show in the README a validation status (failed, succeed) of the particular library. Nevertheless, there should be better solutions.

[TenCoKaciStromy]

If every implementation had a CLI, a universal test could be done.
I personally would like a test like that. I wouldn't miss any changes in the specification.

[akhundMurad]

Also we can implement an GitHub action. However, it's hard to imagine the way of running tests upon the diversity of languages and testing tools

[broothie]

I actually created a workflow that does this! https://github.com/broothie/typeid-ruby/blob/main/.github/workflows/monitor_spec_updates.yml.

It runs on a nightly basis, and it basically just downloads the spec files and creates a PR if there's a diff. The next step would be to make the necessary changes to the implementation to make the specs green again, and merge the PR.

[akhundMurad]

@broothie Nice work! Maybe it is worth adding the reference to this workflow in the README.