Skip to content

[Core] fix MentionEntity parse#105

Merged
Executor-Cheng merged 3 commits into
LagrangeDev:mainfrom
Szzrain:fix/at-parse
Mar 31, 2026
Merged

[Core] fix MentionEntity parse#105
Executor-Cheng merged 3 commits into
LagrangeDev:mainfrom
Szzrain:fix/at-parse

Conversation

@Szzrain
Copy link
Copy Markdown
Contributor

@Szzrain Szzrain commented Mar 31, 2026

No description provided.

Copilot AI review requested due to automatic review settings March 31, 2026 01:25
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to fix MentionEntity parsing so mentions carried via Text.PbReserve (TextResvAttr) are correctly interpreted, including UID-based mentions that don’t include a UIN.

Changes:

  • Made MentionEntity.Uin mutable internally so it can be filled in after parsing.
  • Added IMessageEntity.Postprocess to resolve Uin from Uid when the protocol only provides a UID.
  • Updated Parse to gate mention creation on TextResvAttr.AtType and to capture AtMemberUid when AtMemberUin is missing.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Lagrange.Core/Message/Entities/MentionEntity.cs
Comment thread Lagrange.Core/Message/Entities/MentionEntity.cs
Comment thread Lagrange.Core/Message/Entities/MentionEntity.cs Outdated
@Executor-Cheng
Copy link
Copy Markdown
Contributor

Thanks

@Executor-Cheng Executor-Cheng merged commit ba626dc into LagrangeDev:main Mar 31, 2026
10 of 12 checks passed
@Szzrain Szzrain deleted the fix/at-parse branch March 31, 2026 03:34
Bemly pushed a commit to Bemly/CharonAnchor that referenced this pull request May 3, 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.

[Bug] TextResvAttr.AtMemberUin may not exist causing mention to be resolved to mention_all

3 participants