fix(logger): set utf-8 encoding #223
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CorieW
force-pushed
the
@invertase/fix-logging-unicode
branch
3 times, most recently
from
22075d3 to
54127a4
Compare
CorieW
force-pushed
the
@invertase/fix-logging-unicode
branch
from
54127a4 to
abfa1d5
Compare
pr-Mais
approved these changes
Dec 30, 2024
exaby73
approved these changes
Dec 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To address firebase/firebase-tools#8002
Note: changing
google-events>=0.5.0togoogle-events==0.5.0is due to breaking changes in a later version (than 0.5.0) ofgoogle-eventscausing linting to fail. Failure can be seen here.