Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Text Case Converter: show how identifiers are split into words

Cerrado
  • ¿Algo no está bien?
#409 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@srikar-naidu ya está trabajando en esto.

Desde el 28/10/2026.

  • #418 de @srikar-naidu — fusionado

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement hacktoberfest
What problem does this solve?

The Text Case Converter converts identifiers between naming conventions, but users cannot see how the input was segmented before conversion.

Inputs containing acronyms, digits, or mixed separators can have ambiguous word boundaries. Showing the detected words would help users understand results such as converting XMLHttpRequest to xml_http_request.

Proposed solution

Add a “Detected words” section below the input, showing the word segments used by the existing case-conversion logic.

Scope
  • Reuse the existing word-splitting logic so the displayed segments match the conversion results.
  • Display each segment as a readable token, preserving its original casing.
  • Handle camelCase, PascalCase, acronyms, and supported separators.
  • For multi-line input, show detected words separately for each non-empty line, labeled with its original line number.
  • Explain that acronym and digit boundaries follow the converter’s existing rules.
  • Show a helpful empty state when the input contains no detected words.
  • Keep existing conversion behavior unchanged.
Acceptance criteria
  • XMLHttpRequest displays XML, Http, and Request.
  • user_id displays user and id.
  • HTTP_status_code displays HTTP, status, and code.
  • Digit boundaries match the existing conversion behavior and are covered by tests.
  • Repeated separators and surrounding whitespace do not create empty tokens.
  • Unicode input follows the same rules as the existing converter.
  • The detected words update as the input changes.
  • Multi-line results preserve the association with their source lines.
  • Tokens remain readable in both site themes and are accessible to screen readers.
  • Word segmentation lives in lib/ with tests covering acronyms, digits, separators, Unicode, and multi-line input.
  • All processing happens locally in the browser.
  • npm run lint && npm run test && npm run build pass.

Custom splitting rules, editable tokens, and changes to existing conversion algorithms are outside this issue’s scope.

Fit
  • This can work entirely in the browser with no server or data leaving the tab.
Lenguaje dominante
TypeScript
Estrellas
1
Forks
9
Merge medio
7 h 34 min
PR fusionados (30 d)
195

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codercops/toolbelt

Todos los issues de codercops/toolbelt

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.