Replies: 5 comments 5 replies
-
This would be a great addition, because parsing weird and wonderful textual output of other commands is pretty much the core tenet of Unix scripting. |
Beta Was this translation helpful? Give feedback.
-
That would be great. It would allow building a parser with Babashka and instaparse to validate commit messages to follow the conventional commit specs. I've had this in my mind for a while now as I'm trying to build a full development and CI/CD workflow in Clojure and Babashka instead of mixing it with other tools i.e. based on Node.js. |
Beta Was this translation helpful? Give feedback.
-
Currently running into a use case where I'm trying to parse the output of low-level git commands. I can do this by hand, but instaparse would make it a heck of a lot easier. |
Beta Was this translation helpful? Give feedback.
-
I've made a pod + wrapping library here: https://github.com/babashka/instaparse.bb This can be considered an initial step in playing around with Instaparse + bb. If the pod ends up being spectacularly popular, I'd have a better idea if Instaparse should be included into bb itself at one point. |
Beta Was this translation helpful? Give feedback.
-
I tried making a jaasentaa parser 1st, failed, and then tried instaparse, that worked somewhat better. In my case I wanted to make a parser for "logkeys" files, which I use in order to improve my qmk keyboard layout, |
Beta Was this translation helpful? Give feedback.
-
Upvote or comment if you're interested. It would also be interesting into looking if instaparse could be executed from source.
Beta Was this translation helpful? Give feedback.
All reactions