Skip to content

FIX: reject unsupported demo datasets in export_code#389

Open
biru-codeastromer wants to merge 1 commit intosktime:mainfrom
biru-codeastromer:fix/export-code-supported-demo-dataset-validation
Open

FIX: reject unsupported demo datasets in export_code#389
biru-codeastromer wants to merge 1 commit intosktime:mainfrom
biru-codeastromer:fix/export-code-supported-demo-dataset-validation

Conversation

@biru-codeastromer
Copy link
Copy Markdown
Contributor

Summary

  • reject unsupported supervised demo datasets when export_code is asked to include a forecasting fit example
  • keep valid forecasting datasets like airline working as before
  • add focused regression tests for supported and unsupported dataset paths

Why

export_code_tool(..., include_fit_example=True, dataset=...) currently trusts the raw discovered demo dataset map and can generate misleading forecasting example code for datasets like basic_motions.

Testing

  • .venv/bin/ruff check .
  • .venv/bin/ruff format --check .
  • .venv/bin/pytest tests/test_codegen.py -q
  • .venv/bin/pytest -q

Closes #388

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.

[BUG] export_code accepts unsupported demo datasets for fit examples and generates misleading forecasting code

1 participant