-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docker container to generate parsers and languages #154
Conversation
d2156a2
to
cc143f5
Compare
Branch rebased (explaining the force-push). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe irrelevant thoughts. But thoughts that might help
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Get other reviews
The go parser is currently generated and then formatted. This however requires that go is installed when generating the parser. This added dependency makes code generation more complicated than it needs to be as this is yet another tool people need to install. This in turn makes #154 more complicated than it needs to be. By making the code generator generate formatted code we avoid this problem all together.
The go parser is currently generated and then formatted. This however requires that go is installed when generating the parser. This added dependency makes code generation more complicated than it needs to be as this is yet another tool people need to install. This in turn makes #154 more complicated than it needs to be. By making the code generator generate formatted code we avoid this problem all together.
Cheers @ehuelsmann ! Took me a while to get to this but this is actually really good improvement. A belated thanks for kicking it off. |
🤔 What's changed?
A dockerized version of Berp.
⚡️ What's your motivation?
The
cucumber/build
container is huge. Most people only need it to run Berp. So, instead of downloading and maintaining a multi-gigabyte container, lets use a lean one with exactly one purpose.🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
This container likely causes permissions conflicts: the
cukebot
user has hard-coded UID 1000 whereas not everybody will be running as that user. The release container had trickery to be able to run "as the current user". Is it easy to transplant and do we want/need that? (was it even in the container? Or was it in the makefile before?)📋 Checklist: