poetry lock --check has no output

[DetachHead]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: windows 10
• Poetry version: 1.2.0a2

Issue

it would be nice if there was some sort of output other than just the exit code

> poetry lock --check

> echo %errorlevel%
1

perhaps an error message like

Error: poetry.lock is out of date. run `poetry update` to fix it

[radoering]

Sounds good. I am just wondering if poetry update is the most suitable recommendation or if poetry lock [--no-update] is better suited? It seemed natural to me to call lock if lock --check failed. That way you can decide if you only want to bring pyproject.toml and poetry.lock in line (without updating already locked dependencies) or if you want to update these, too. As far as I understand, poetry lock is the same as poetry update --lock. Probably, the advantage of poetry update over poetry lock is that you don't have to call poetry install separately.

[artemrys]

@radoering I can take this one, it seems to be an easy change. Do we just need to add some a log here

poetry/src/poetry/console/commands/lock.py

Lines 39 to 44 in 335f209

	if self.option("check"):
	return (
	0
	if self.poetry.locker.is_locked() and self.poetry.locker.is_fresh()
	else 1
	)

and update / create tests?

[radoering]

@artemrys: Yes, that seems to be the correct part of the code. Tests are in test_lock.py. There are also tests for other commands that already check output. You can use these tests as a guide.

Further, I think in case of success (if poetry.lock is consistent with pyproject.toml, exit code 0) there should be a message, too.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.