jargonsdev / jargonsdev/jargons.dev
Implement logic to disable submission button in the editor when content is empty
- Dominant language
- MDX
- Stars
- 56
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Currently, users can submit a new word without entering any content or title. To improve the quality of submissions, we should implement a logic that disables the submission button when either the content or title field is empty. Additionally, we should consider implementing a minimum input length requirement for the content field to ensure meaningful contributions.
**Related Files:**
- https://github.com/babblebey/jargons.dev/blob/main/src/pages/editor/new/index.astro
- https://github.com/babblebey/jargons.dev/blob/main/src/components/islands/word-editor.jsx
**Steps:**
1. Implement a check in the editor add new word action to disable the submission button if the content or title field is empty.
2. Display a message or tooltip to inform users that both fields are required for submission.
3. Consider implementing a minimum input length requirement for the content field (e.g., at least 50 characters).
**Expected Behavior:**
- The submission button should be disabled if the content or title field is empty.
- Users should receive a clear message or tooltip indicating that both fields are required.
- The content field should require a minimum of 50 characters for submission.
**Additional Information:**
- This enhancement will help improve the quality of contributions by ensuring that users provide meaningful content when submitting new words.
- I thought that at least 50 characters can assure us of a meaningful content; is this too much or less!? kindly share your thought 😉
Contributor guide
Research direction
Start with src/pages/editor/new/index.astro and src/components/islands/word-editor.jsx, then trace the add-new-word action and its current submission controls. Done means empty title or content prevents submission, users see a required-fields message, and the agreed minimum content length is enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100