Skip to content

Unifying forecasting CLI and Schema field descriptions #1864

Description

@BelhsanHmida

Description:

The forecasting parameters currently have their descriptions defined twice:

  • in the CLI command decorators.
  • in ForecasterParametersSchema.

This duplication increases maintenance costs and risks inconsistencies.

We should introduce a mechanism where CLI options are automatically generated from the Marshmallow schema (or vice versa), establishing a single source for forecasting parameter metadata.

This was raised during a review of PR #1824

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions