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
{{ message }}
This repository has been archived by the owner on Sep 7, 2021. It is now read-only.
In #14 we're developing the first cli tool that can be used to turn the .md and .yaml files into .json files.
The next natural thing to do, especially from a kuma perspective, is to now glob for all these .json files and one by one, do a lookup of its recipe and then do something with that. E.g. extract the bits it needs to turn it into kuma content.
So what else do we need Python for. Today, the only entrypoint I see is the validate.py script.
Regarding #14@wbamberg mentioned that that script assumes that the integrity of all the core content (e.g. .md and .yaml files) is perfect. And I think that's right.
I would be open to rewriting validate.py to validate.js and reduce this whole project to become a 100% Node project.
The text was updated successfully, but these errors were encountered:
In #14 we're developing the first cli tool that can be used to turn the .md and .yaml files into .json files.
The next natural thing to do, especially from a kuma perspective, is to now glob for all these .json files and one by one, do a lookup of its recipe and then do something with that. E.g. extract the bits it needs to turn it into kuma content.
So what else do we need Python for. Today, the only entrypoint I see is the
validate.py
script.Regarding #14 @wbamberg mentioned that that script assumes that the integrity of all the core content (e.g. .md and .yaml files) is perfect. And I think that's right.
I would be open to rewriting
validate.py
tovalidate.js
and reduce this whole project to become a 100% Node project.The text was updated successfully, but these errors were encountered: