[UI] Plan and Apply commands with additional options

[mykalmax]

• Include additional options when running plan
• Include additional options when applying plan
• Pass change category when applying plan
• Set default dates when running plan first time
• Disable and set to defaults not applicable additional options on initial run
• Refactor Plan shared state into Context to keep state closer to the Plan component
• Add hints and messaging based on different additional options

[mykalmax]

Need some help to understand how to pass restate_models, currently sending from UI just a coma-separated string but plan commands expects t.Iterable[str]

[vchan]

You can use a Pydantic validator to parse the comma separated string into a list. So you'd use a Pydantic model for inputs, which means not using query parameters but a json post body, then add a validator for restate_models that parses the string to a list. It'd look something like this

@validator("restate_models")
def validate_restate_models(cls, v: str | list[str]) -> list[str]:
    if isinstance(v, str):
        return v.split(",")
    return v

[vchan]

Looking good on the server side.

[vchan]

Does this work? I'd normally create a Pydantic model, e.g. ApplyInput, to encapsulate the POST body. It's how the FastAPI documentation usually does it as well.

[vchan]

See my comment above regarding using a Pydantic model.

[vchan]

Let's use a more descriptive name. Maybe PlanOptions? And if you add ApplyInput and/or PlanInput, you can subclass PlanOptions. Or rename this to PlanInput and ApplyInput can extend it.