Tracking: Syncing exercises to problem specifications

[mk-mxp]

Using configlet sync at the time of writing is a wall of warnings. These are things to sync. I will extract one issue for each exercise, but that takes some more time.

To sync an exercise with problem specifications, take these steps:

• Run bin/configlet sync -u -e <slug> --yes --docs --filepaths --metadata --tests include (updates the Markdown files and maybe tests.toml)
• Drop strict types comments from test file and example code (these are useless)
  • Keep the comment in the students stub file. And the directive itself shall be in all PHP files, too.
• Add and sync test meta data to tests (uuid in DocBlocks / #TestDox())
• Add exercise to bin/auto-sync.txt to keep it in sync (keep the file alphabetically sorted)
• Decide on adding / adjusting / ordering test cases to match current problem specs
• If you wish, add your GitHub handle to the list of contributors in exercises/practice/<slug>/.meta/config.json

Do not redesign the student's interface or add test cases that would invalidate existing community solutions. These are extra tasks, which should be discussed in advance.

• Sync variable-length-quantity #976
• Sync simple-cipher #987
• Sync robot-name #994

[tomasnorre]

Would it be possible to create the issues automatically with the GitHub API?

[tomasnorre]

This is basically what I have done a few times for the #48in24 exercises right?

If so I can start from the top and sync them. It will take some time, and have some less productive times now and then, but I can do it.

I one of you will create the issues, I will try to keep up to date with resolving them.

[mk-mxp]

Yes, it is mostly the same as for #48in24. I haven't removed the now deprecated exercises from this list.

I'll make some issues the upcoming week, but I don't have as much time as you have to review them quickly. This month is filled with business travelling and consulting activities...