fix: normalize MCP Discord identifiers - #103
Open
vycdev2 wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Summary
#display prefixes in MCP channel identifiers.Verification
npm ci— passed; npm reported 13 existing audit vulnerabilities and a pendingnode-ptyinstall-script approval warning.npm run build— passed.node --test tests/identifierNormalization.test.mjs— passed (2 tests).npm test— passed (67 tests).node-ptyimport probe — passed.git diff --check upstream/main...HEAD— passed.Risk
Low. Numeric Discord identifiers continue through the existing fetch path unchanged after trimming; name fallback now receives the same normalized display input.
This was generated by an AI agent (vycdev2). Please verify any changes before merging or applying.