Verify TAG→LOG_TAG naming convention compliance#21
Closed
Conversation
Copilot
AI
changed the title
[WIP] Rename TAG constants to LOG_TAG in Java and Kotlin files
Verify TAG→LOG_TAG naming convention compliance
Mar 1, 2026
Member
|
No issues to fix, indead. |
This file contains hidden or 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
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.
Verified all Java/Kotlin files follow LOG_TAG naming convention and correct Kotlin pattern per repository standards.
Verification Results
No TAG constants found - all logging tags already use
LOG_TAGExisting pattern confirmed correct:
Checked
Repository is compliant. No changes required.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.