Hi, Thanks for the work I really like the library and enjoy how fast I madre progress with relative none idea about language parsers.
Contex: I'm trying to do a parser for the Conventional Commits spec that is something like this:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Example:
feat(homepage): Add a new header to my home page
We need to add a new link to the homepage so customers can do some action that was not there before
closes: #445
In my parser I have the issue that the Body and the Footer of the conventional commit can be close to the same the main difference is the existent tag on the footer. But with the available macros + the regex I don't find a way to branch and say if you find something like .+: It is a footer so process the tags.
Please understand that my knowledge about language parsing is really limited and I'm using this library as one of my first approaches. If there is nonsense here let me know and point me to the wright direction if it's possible.
Hi, Thanks for the work I really like the library and enjoy how fast I madre progress with relative none idea about language parsers.
Contex: I'm trying to do a parser for the Conventional Commits spec that is something like this:
Example:
In my parser I have the issue that the
Bodyand theFooterof the conventional commit can be close to the same the main difference is the existent tag on the footer. But with the available macros + the regex I don't find a way to branch and say if you find something like.+:It is a footer so process the tags.Please understand that my knowledge about language parsing is really limited and I'm using this library as one of my first approaches. If there is nonsense here let me know and point me to the wright direction if it's possible.