dotnet/roslyn

APIs which contain oblivious nullability should indicate that in Quick Info

Open

#80,875 建立於 2025年10月24日

在 GitHub 查看
 (4 留言) (1 反應) (0 負責人)C# (20,414 star) (4,257 fork)batch import
Area-IDEhelp wanted

描述

Recently we made a change to give a heads up when interacting with nullable-oblivious variables:

It would be useful if this information were also conveyed when looking at a signature that contains oblivious nullability:

貢獻者指南

技術棧
csharp
領域
developer experiencetooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C# nullabilityRoslyn IDE APIsQuick Info
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
Investigate the previous change that added the nullable oblivious warning for variable Quick Info. Identify the corresponding code for method signature Quick Info in Roslyn's IDE layer, e.g., in src/Features/LanguageServer/QuickInfo or src/EditorFeatures/Core/. Look for where signature help is generated and add similar logic to display 'oblivious' annotation for nullable parameters and return types. Review any existing tests for Quick Info to ensure the new behavior is covered.
APIs which contain oblivious nullability should indicate that in Quick Info · dotnet/roslyn#80875 | Good First Issue