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

misc: reword log #384

Merged
merged 1 commit into from
Aug 13, 2024
Merged

misc: reword log #384

merged 1 commit into from
Aug 13, 2024

Conversation

ComradeVanti
Copy link
Collaborator

The log in question was printed when the upmconfig does not contain an entry for the primary registry. This is usually expected, since usually the primary registry is openupm and you dont need auth for it. Still you would get a warning that openupm could not be parsed. But actually this log just means that there was no entry.

The log was now reworded and also is only shown on the verbose level. Also we now only show this log when using a custom registry, since, again, openupm will never need auth.

The log in question was printed when the upmconfig does not contain an entry for the primary registry. This is usually expected, since usually the primary registry is openupm and you dont need auth for it.
Still you would get a warning that openupm could not be parsed. But actually this log just means that there was no entry.

The log was now reworded and also is only shown on the verbose level. Also we now only show this log when using a custom registry, since, again, openupm will never need auth.
@ComradeVanti ComradeVanti merged commit 0651101 into master Aug 13, 2024
6 checks passed
@ComradeVanti ComradeVanti deleted the upm-config-log branch August 13, 2024 17:20
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.

1 participant