Skip to content

Verify TAG→LOG_TAG naming convention compliance#21

Closed
Copilot wants to merge 1 commit intomasterfrom
copilot/rename-tag-constants
Closed

Verify TAG→LOG_TAG naming convention compliance#21
Copilot wants to merge 1 commit intomasterfrom
copilot/rename-tag-constants

Conversation

Copy link

Copilot AI commented Mar 1, 2026

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_TAG

Existing pattern confirmed correct:

private val LOG_TAG: String = SourceUtils::class.java.simpleName

Checked

  • 66 Java/Kotlin files scanned for TAG constant declarations
  • Kotlin LOG_TAG declarations verified for non-nullable String type
  • No getLogTag() methods requiring updates

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.

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
@mmathieum
Copy link
Member

No issues to fix, indead.

@mmathieum mmathieum closed this Mar 1, 2026
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