Uh oh!
There was an error while loading. Please reload this page.
Assessment: Review pipeline stages + config save/tag fixes - #217
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Issue: #216
Summary
Wizard navigation order
Evaluation step's forward button previously said "Next: Review", but it jumping past to the Post Processing step. Now it says "Next: Post Processing", so the order is Mapper → Eliminatory → Evaluation → Post Processing → Review.
Review Stage previously showed only Dataset, Columns, LLM Input, Configs, and Response Format — the two optional stages were invisible, so a user couldn't confirm what Eliminatory and Post Processing would do (or that they were skipped). Review now also shows:
Eliminatory — Topic Relevance (columns, documents, prompt preview) and Duplicate Detection (columns). Shows "Skipped" when nothing is enabled.
Post Processing — computed columns, filters, and sort rules. Shows "Skipped" when nothing is configured.
Saving an Evaluation config
When saving a new config, the old code looked for an existing config with the same name and, if found, created a new version under it instead — wrong behavior, since this is the "New" flow. Now it always creates a new config, so a duplicate name correctly raises a name-conflict error.