You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the specification repository is using it's own schemas to generate the documentation, we can now use those schemas in the validator instead of having our own.
I dislike git submodule, but I don't see a better way. Since the spec schemas is based upon the one here I suspect this will be an easy transition.
Any alternatives to git submodule? If no, we can try to get this working during grcon next week.
The text was updated successfully, but these errors were encountered:
One alternative to git submodule is for the github action that publishes to pypi to clone the spec repo as part of building the package, and then for folks doing local dev there can be a line in the install instructions that involves cloning it. There may also be some pyproject.toml way to do it, I know that you can specify a dependency by giving it the github url but we're not talking about a python package, it just needs the json schema. The other thing is that json schemas are supposed to be available via url, so if we standardize the url its available at we can hardcode it in this repo.
I like the idea of having the URL, but will there be a separate URL for each version of the spec? I wouldn't want the spec to change and break the python module. At least with submodule you explicitly pin a commit value.
Alright I just tried something on the main repo to see if it would work- what we can do is use githubs release system and the fact you can get to any raw file using the tag in the URL, to deal with version control of the json schema without going out of our way. Eg the latest one is- https://raw.githubusercontent.com/sigmf/SigMF/v1.2.2/sigmf-schema.json
Now that the specification repository is using it's own schemas to generate the documentation, we can now use those schemas in the validator instead of having our own.
I dislike
git submodule
, but I don't see a better way. Since the spec schemas is based upon the one here I suspect this will be an easy transition.Any alternatives to
git submodule
? If no, we can try to get this working during grcon next week.The text was updated successfully, but these errors were encountered: