Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat!: Rename "TextInputSetting" to "TextAreaSetting" and added TextInputSetting #414

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from

Conversation

Trevlouw
Copy link

Description

Describe the changes
valera named the wrapper for the SSTextArea setting "TextInputSetting" even though this setting only displays text from the server (you can't input text into it) so when I wanted to make something for a text area I asked on the discord, got told to make a PR for the SSPlaintextSetting so I spent like 30m trying to do so and eventually succeeding, the problem is, I wanted to use a SSTextArea the entire time but valera named it wrong 😭 😭 😭 😭 so I spent 30m trying to make something that nobody asked for when what I wanted already existed. So, because I made the actual TextInputSetting and the previous TextInputSetting should've been renamed to TextAreaSetting, I made this PR where the TextInputSetting is an actual text input and added the TextAreaSetting which is a text area.

What is the current behavior? (You can also link to an open issue here)
TextInputSetting class name is misleading, there is no SSS for an actual text input

What is the new behavior? (if this is a feature change)
TextInputSetting now represents the setting where you can input a string, there is now TextAreaSetting which replaces the old TextInputSetting's role

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Yes, I renamed the TextInputSetting so devs just need to change there code from new TextInputSetting(args) to TextAreaSetting(args)

Other information:
I am REALLY bad at this so please proofread what I did 🙏


Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentations

Submission checklist

  • I have checked the project can be compiled
  • I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

  • I have checked no IL patching errors in the console

Other

  • Still requires more testing

@github-actions github-actions bot added the API label Jan 25, 2025
@Trevlouw Trevlouw changed the title Rename "TextInputSetting" to "TextAreaSetting" and added TextInputSetting feat: Rename "TextInputSetting" to "TextAreaSetting" and added TextInputSetting Jan 25, 2025
@Trevlouw
Copy link
Author

I forgor to add feat 😩

@Trevlouw Trevlouw changed the title feat: Rename "TextInputSetting" to "TextAreaSetting" and added TextInputSetting feat!: Rename "TextInputSetting" to "TextAreaSetting" and added TextInputSetting Jan 26, 2025
@louis1706
Copy link

I forgor to add feat 😩

is it possible than you make a pr that add the feature without breaking change (so different naming)

@VALERA771
Copy link

VALERA771 commented Jan 27, 2025

Add TextInputSetting to Create method nvm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants