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
When a contributor updates gherkin-languages.json they'll run make copy-gherkin-languages to copy this file and/or generate derived for each implementation. This process should be light weight only depend on a few tools such as jq, however for Perl, this process currently depends on Perl.
This problem would be solved by using the sames solution as the one i suggested in #32. I guess I could try to generate valid Perl from inside jq, but I wonder if that's worth the effort, or that we're really trying to solve the wrong problem here...
🤔 What's the problem you've observed?
When a contributor updates
gherkin-languages.json
they'll runmake copy-gherkin-languages
to copy this file and/or generate derived for each implementation. This process should be light weight only depend on a few tools such asjq
, however for Perl, this process currently depends on Perl.gherkin/perl/Makefile
Lines 32 to 37 in 1cc2ef0
✨ Do you have a proposal for making it better?
Consider using
jq
instead of perl to generateLanguages.pm
instead. For example see:https://github.com/cucumber/gherkin/blob/1cc2ef0153603c5e51818b59ff6d632238491226/go/dialects_builtin.go.jq
The text was updated successfully, but these errors were encountered: