[BUG] Teams / Graph API Regression: "codeBlockEditor" vs <codeblock> in HTML Content Results
还没有人认领这个 Issue。
评估
调研方向
Start by reproducing the issue with a Teams chat message containing inline code followed by a triple-backtick block, then query it with GET /v1.0/chats/{id}/messages/{msg}. The payload names no files, tests, or SDK entry point; done would require the returned HTML to preserve each code block's own content instead of reusing an earlier code element.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
[I'm not sure if the "Javascript SDK" is the right place for this, because it's a server-side bug, but here goes... If there's a better repository, I'd be happy to repost it there, thanks!]
Within the past week or so (January 2026) whenever I GET /v1.0/chats/{id}/messages/{msg}, it seems that "triple-backtick" code blocks have gone from being sent as <p itemtype="http://schema.skype.com/CodeBlockEditor"> elements to dedicated <codeblock> tags, with embedded <code> inside...
That wouldn't be a problem, EXCEPT I've noticed that when there's another <code> tag earlier in the message content, it replaces the contents of any subsequent <codeblock><CODE>...</CODE></codeblock> blocks.
To wit:
The `message` is:
```
Hello, world!
```
Produces the following snippet of JSON:
"body": {
"content": "<p>The <code>message</code> is:</p>\n<codeblock class=\"PlainText\"><code>message</code></codeblock>",
"contentType": "html"
}
Note that the second message does NOT say "Hello, world!"
This also happens for other "triple-backtick" code blocks:
```
Line One
```
Line `Two`
```
Line Three
```
Becomes "One, Two, One" :-(
Expected behavior
In the first example, I would expect to see <codeblock><code> Hello, world!</code></codeblock>
How to reproduce
Send a Teams message (chat or channel) with the markup:
This is `inline code`
```
This is a block
```
Then query that message via the Graph API; you'll see that it returns the wrong results.
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
No response
Configuration
No response
Other information
Like I say, I tried looking for a more API-related repository, but github.com/microsoftgraph lists, like, 230 different repos, and I only made it through ~3 pages of results before I gave up... «sigh»
- 主要语言
- TypeScript
- 星标
- 833
- 派生
- 240
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoftgraph/msgraph-sdk-javascript 的其他 Issue
-
status:waiting-for-triage
难度 1/5 1 小时以内 新手友好度 62/100
-
Is anyone here? 未关闭
难度 4/5 3-5 天 新手友好度 25/100
microsoftgraph/msgraph-sdk-javascript#2005 · 1 个 reaction ·
-
status:waiting-for-triage
难度 5/5 一周以上 新手友好度 42/100
-
status:waiting-for-triage type:bug
难度 3/5 1-2 天 新手友好度 48/100
microsoftgraph/msgraph-sdk-javascript#1999 · 2 条评论 · 1 个 reaction ·
-
status:waiting-for-triage type:bug
难度 4/5 3-5 天 新手友好度 45/100
查看 microsoftgraph/msgraph-sdk-javascript 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
check:passed streams:add
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
usability
难度 2/5 1-3 小时 新手友好度 68/100
inmanta/web-console#7367 ·