Default baseline file?

[ro0NL]

Hi,

From https://psalm.dev/docs/running_psalm/dealing_with_code_issues/#using-a-baseline-file

I found running psalm --set-baseline does nothing, where i expected it would took the baseline file as configured in psalm.xml (errorBaseline) 🤔 since providing the same value (as documented) does work. However i thought the docs did to initally generate it also :)

Also i believe the term "update" is rather implicit: "to remove references to things that have been fixed", if not confusing vs. "set".

WDYT?

[orklah]

Not sure I followed you.

--set-baseline expect a filename, it will add the filename to your current xml config and rewrite the complete baseline in it
--update-baseline does not expect an argument and it will only remove outdated issues (it will not add new ones)

If the suggestion is to be able to remove the filename for --set-baseline, then it's a duplicate of #5831. If there is another thing, can you explain it further?

[ro0NL]

Ack. I have the same POV as #5831 (comment) 👍

I do believe an update can be interpreted as both "add" and "remove".

IIUC we could add a third option, eg.--sync-baseline [optional-filename] that invokes both steps.

My usecase is dusting the develop branch :) eg. updating basefile with the current branch's status quo.

[orklah]

Feel free to propose a PR to make the filename optional, I think this would be accepted. I'll close this as duplicate of #5831 then