-
-
Notifications
You must be signed in to change notification settings - Fork 698
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
Move messages to stand-alone repo #2029
Comments
Todo list (for at least go, java, javascript, perl, php and ruby - dotnet is ignored for now, elixir may require additional work in parallel of #1952):
Depending on the status of the elixir piece of work, do not forget to
|
The part regarding the README which was copied from the parent folder will be managed later. It is part of the TODO list here: cucumber/common#2029
* Rework code generation for Ruby * Rework code generation for Javascript * Rework code generation for Java * Rework code generation for Go * Rework code generation for Perl The part regarding the README which was copied from the parent folder will be managed later. It is part of the TODO list here: cucumber/common#2029 * Add some requirements checks in java makefile * Rework code generation for PHP * Rework root Makefile * Add validation of schemas into root makefile * Add a workflow to check there is no need to generate code * Fix workflow * Fix set up of node in test-codegen workflow * Add missing checkout step into test-codegen workflow * Fix 'composer install' instruction in test-codegen workflow * Update messages.md to test the test-codegen workflow * Run clean-all before generate-all in test-codegen workflow * Fix messages.md to fix the test-codegen workflow
@aurelien-reeves thanks for all your work on this! I've had a busy few weeks and am only just picking this up. I don't quite have enough context to help with the task about synchronizing the readmes - do you mean we could copy / paste a standard README file manually into each language sub-folder? Or did you mean something more fancy and automated? I've made a start on the release workflows, but we will need help from Wannes, Ciaran and Erik to get the Elixir, PHP and Perl releases working I think. |
@mattwynne regarding the readmes, I had no idea in mind. I just wanted to avoid missing readmes with npm or such package managers. That could be done manually. For the release workflows:
|
* Rework code generation for Ruby * Rework code generation for Javascript * Rework code generation for Java * Rework code generation for Go * Rework code generation for Perl The part regarding the README which was copied from the parent folder will be managed later. It is part of the TODO list here: cucumber/common#2029 * Add some requirements checks in java makefile * Rework code generation for PHP * Rework root Makefile * Add validation of schemas into root makefile * Add a workflow to check there is no need to generate code * Fix workflow * Fix set up of node in test-codegen workflow * Add missing checkout step into test-codegen workflow * Fix 'composer install' instruction in test-codegen workflow * Update messages.md to test the test-codegen workflow * Run clean-all before generate-all in test-codegen workflow * Fix messages.md to fix the test-codegen workflow
* Rework code generation for Ruby * Rework code generation for Javascript * Rework code generation for Java * Rework code generation for Go * Rework code generation for Perl The part regarding the README which was copied from the parent folder will be managed later. It is part of the TODO list here: cucumber/common#2029 * Add some requirements checks in java makefile * Rework code generation for PHP * Rework root Makefile * Add validation of schemas into root makefile * Add a workflow to check there is no need to generate code * Fix workflow * Fix set up of node in test-codegen workflow * Add missing checkout step into test-codegen workflow * Fix 'composer install' instruction in test-codegen workflow * Update messages.md to test the test-codegen workflow * Run clean-all before generate-all in test-codegen workflow * Fix messages.md to fix the test-codegen workflow
No description provided.
The text was updated successfully, but these errors were encountered: