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
{{ message }}
Repository navigation
Bug / Unexpected Behavior: Methods starting with Set/Reset are interpreted as property setters #4
Describe the bug / unexpected behavior
A C# method named SetMode(string) gets automatically interpreted by the bridge as the setter of a Mode property instead of remaining a callable method. This forced me to rename all such methods to Choose* (e.g., ChooseMode, ChooseAccent) and leave warning comments across my view models.
Steps to reproduce
.
Expected behavior
Describe the solution I'd like
Either emit a build warning when this collision occurs or provide an explicit opt-out attribute like [Qt.Method] so methods aren't mistaken for property setters.
Activity
github-actions commentedon Nov 12, 2026
Thank you for the report. It is now tracked as QTBRIDGES-461 in the Qt bug tracker. Please follow up there.