Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: log up-to-date when single entry #257

Merged
merged 2 commits into from
Mar 11, 2024

Conversation

blaggacao
Copy link
Contributor

Context

discussion in #253 (comment)

@blaggacao blaggacao force-pushed the feat/feedback-on-single-item branch 2 times, most recently from 8445e17 to f221b7d Compare March 8, 2024 13:01
oldvers: VersData, r: Result,
oldvers: VersData,
r: Result,
log_noop: bool,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a better name for it. Maybe verbose since verbosity is indeed increased.

Comment on lines 388 to 392
if log_noop:
# provide visible user feedback if it was the only entry
logger.info('up-to-date', name=r.name, version=r.version, url=r.url)
else:
logger.debug('up-to-date', name=r.name, version=r.version, url=r.url)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use logger.log(level, ...) to avoid duplicate code.

@lilydjwg lilydjwg force-pushed the feat/feedback-on-single-item branch from 1ce6324 to 887665d Compare March 11, 2024 12:53
this ensures the newver file keeps untouched records
@lilydjwg lilydjwg force-pushed the feat/feedback-on-single-item branch from 887665d to 9dd7fb1 Compare March 11, 2024 13:26
@lilydjwg lilydjwg merged commit 9dd7fb1 into lilydjwg:master Mar 11, 2024
22 checks passed
@blaggacao blaggacao deleted the feat/feedback-on-single-item branch March 11, 2024 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants