David de la Iglesia Castro

Unless we expand the scope, I believe we don't really need a `log_model` method but just add `mlem.api.save` calls in the integrations

> If we're going to call `mlem.api.save` under the hood in the DVCLive, then I assume yes. @daavoo, do you have a vision how the integration should look like for...

> @daavoo, the code you mention should be executed inside DvcLiveCallback(), am I correct? Yes we would need to add it to each integration callback

I think it makes sense as default behavior, but doesn't really fix the use case of wanting to visualize image updates across epochs (https://github.com/iterative/vscode-dvc/issues/1640). A nested structure makes sense for...

> Related to @iesahin 's work on #3414 Not sure I follow. I don't see any content regarding `templating` or `foreach` in the P.R.

> One tricky issue here is that we update `params.yaml` or other params files with the `+` and `~` syntax to add/remove parameters, but we don't update `dvc.yaml`. > >...

@dberenbaum Updated with examples for basic syntax and warning about `dvc.yaml`

> Looks good @daavoo! Can you resolve the merge conflict and do one more iteration? I think we could merge as is, but since there is no rush here, let's...

Merging to move forward. Don't hesitate to post additional comments and I will address them in subsequent P.R.

> what should we copy in this case? We could leave this decision up to the writer, which can decide whether to split code and output into 2 separated blocks?