Skip to content

chore: Convert problem.yaml to new schema#172

Open
olafmersmann wants to merge 4 commits intopush-zmvqzzrwnlupfrom
pr-convert-problems.yaml
Open

chore: Convert problem.yaml to new schema#172
olafmersmann wants to merge 4 commits intopush-zmvqzzrwnlupfrom
pr-convert-problems.yaml

Conversation

@olafmersmann
Copy link
Copy Markdown
Collaborator

Adds an LLM generated generator for the problems defined in the old
problem.yaml to generate a new style problem.yaml. For future fixes, it is
probably best to update examples/problem.py, regenerate the yaml and then merge
it with the old yaml by replacing entries based on id. That way additional
entries added later are not clobbbered.

@olafmersmann
Copy link
Copy Markdown
Collaborator Author

This is not ready for merging. It is an LLM generated work in progress. Note all the #FIXME comments that should reviewed / fixed before merging.

@olafmersmann olafmersmann force-pushed the pr-convert-problems.yaml branch 3 times, most recently from ffdc3f6 to 41f91ba Compare April 22, 2026 14:06
@olafmersmann olafmersmann force-pushed the pr-convert-problems.yaml branch from 41f91ba to 5cc8891 Compare April 22, 2026 14:29
@olafmersmann olafmersmann force-pushed the pr-convert-problems.yaml branch 2 times, most recently from 0a931a4 to fff80f0 Compare April 22, 2026 20:54
@olafmersmann olafmersmann force-pushed the push-zmvqzzrwnlup branch 2 times, most recently from 240bfa7 to 3343cd8 Compare April 22, 2026 21:25
@olafmersmann olafmersmann force-pushed the pr-convert-problems.yaml branch from fff80f0 to a3059ed Compare April 22, 2026 21:26
Copy link
Copy Markdown
Collaborator

@kvdblom kvdblom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Create issue, then merge ready. Probably first combine with #164 , then to main.

Comment thread examples/problems.py
Every entry from the original YAML is preserved as a `#!` comment block
directly above the Python object(s) it was converted into. Where the
original YAML carried information that does not fit into the new schema,
a `FIXME` comment is used to flag the loss.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Create issue that specifically requests the FIXME comments in this file to be resolved.

Rudimentary design document and reference for the new schema that attempts to
summarize the discussion at the OPL hackathon in April. The core structure was
written by the author, then fleshed out using Claude and finally reviewed by
again the author.

Co-Authored-By: Claude Opus 4.7
Adds an LLM generated generator for the problems defined in the old
problem.yaml to generate a new style problem.yaml. For future fixes, it is
probably best to update examples/problem.py, regenerate the yaml and then merge
it with the old yaml by replacing entries based on id. That way additional
entries added later are not clobbbered.
@olafmersmann olafmersmann force-pushed the pr-convert-problems.yaml branch from a3059ed to 9a9655f Compare April 23, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants