You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2310 textbox should not apply localization on assignment (#2311)
* First pass at fixing localization on assignment
Refactoring and XML docs
* Added SetTextNoTranslate to TextRuntime
Fixed initial assignment of text using localization for "" (potentially)
Copy file name to clipboardExpand all lines: .claude/code-style.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,3 +10,4 @@
10
10
* Do not use `(not, used)` in lambdas, even if you see it elsewhere in the code. Instead use `(_,_)`.
11
11
***Unit tests: always use explicit types, not `var`**. Every local variable declaration in a unit test method must use the concrete type (e.g., `ComponentSave button = new ComponentSave { ... }`, not `var button = new ComponentSave { ... }`).
12
12
***Unit tests: prefer `async Task` over blocking**. Test methods that call async code must be declared `async Task` and use `await`. Never use `.GetAwaiter().GetResult()`, `.Result`, or `.Wait()` in tests.
13
+
***XML documentation**: Always include `/// <summary>` on new publicly-facing types, methods, properties, and events. Do not doc private or internal members unless their behavior is non-obvious. Before writing a summary, check whether the member overrides or implements a base class or interface member — if so, use `/// <inheritdoc/>` instead. When a public member is primarily called internally (e.g., by a service or manager), say so in the summary and point to the preferred user-facing API.
0 commit comments