Skip to content

Reply to naming convention question on TextInput.GetText() - #31

Closed
kcjonson with Copilot wants to merge 1 commit into
fix/text-input-key-repeat-and-selection-bugsfrom
copilot/sub-pr-30
Closed

kcjonson with Copilot wants to merge 1 commit into
fix/text-input-key-repeat-and-selection-bugsfrom
copilot/sub-pr-30

Conversation

Copilot AI commented Nov 26, 2025 •

Copy link
Copy Markdown
Contributor

Responded to maintainer's question about whether GetText()/SetText() should be renamed to GetValue()/SetValue() in the TextInput component.

Recommendation: Keep current naming

  • text is idiomatic in C++ UI frameworks (Qt, SFML) and game engines (Unreal, Unity)
  • value is HTML/web framework convention (React, Vue)
  • Current naming aligns with existing codebase pattern (Button::m_label)

No code changes required.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI changed the title [WIP] Fix key repeat support and TextInput selection bugs Reply to naming convention question on TextInput.GetText() Nov 26, 2025
Copilot AI requested a review from kcjonson November 26, 2025 16:44
@kcjonson kcjonson closed this Nov 26, 2025
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.

2 participants