Skip to content

Conversation

@selimdoyranli
Copy link

πŸ”— Linked issue

#29

❓ Type of change

  • ✨ New feature (a non-breaking change that adds functionality)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • βͺ Revert (when codes are rolled back)
  • πŸ“– Documentation (updates to the documentation, readme, or JSdoc annotations)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

  • autosize user input, supports ctrl+enter combination

image

textarea

πŸ“ Checklist

  • I have linked an issue
  • My code follows the style guidelines of this project
  • My changes are linted, i didn't use bypass for this codes
  • I have performed a self-review of my own code
  • I have done pair programming for my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes

πŸ§ͺ How has this been tested?

--

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.

1 participant