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

ER: Remove unused `search` id query selectors

Abierto Apto para principiantes
  • ¿Algo no está bien?
#8,803 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
88/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
frontend

Línea de trabajo

Abre assets/js/current-projects.js y busca los tres selectores que apuntan al id #search; compáralo con _includes/current-projects.html para confirmar que ese id no está presente. Elimina todas las apariciones de document.querySelector('#search') y, después, verifica que no queden selectores de ese tipo en el archivo JavaScript.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Complexity: Small Draft ER Issue Making: Level 1 P-Feature: Projects page ready for merge team role: back end/devOps size: 0.25pt
Emergent Requirement - Problem

In assets/js/current-projects.js, there are three query selectors that select an id named search. However, in _includes/current-projects.html, there is no id for search.

We must remove any query selectors for search in assets/js/current-projects.js since it is an unused id.

Issue you discovered this emergent requirement in
  • #8466
  • Issue was pointed out in this comment for the PR of the original issue
Date discovered

9/19/2026

Did you have to do something temporarily
  • YES
  • NO
Who was involved

@ldaws003 @castillios

What happens if this is not addressed

Any deprecated IDs may continue to bloat the codebase if left unaddressed.

Resources
Recommended Action Items
  • Make a new issue
  • Discuss with team
  • Let a Team Lead know
Potential solutions [draft]

  • Create a small issue that lists the 3 instances of document.querySelector('#search') and their corresponding line numbers to be removed from assets/js/current-projects.js.

  • In your issue body under the Instructions section, include before and after code snippets as follows:

    Line 105 before:

    const inputEl = document.querySelector('#search-desktop') || document.querySelector('#search-mobile') || document.querySelector('#search');

    Line 105 after removing document.querySelector('#search'):

    const inputEl = document.querySelector('#search-desktop') || document.querySelector('#search-mobile');

    Lines 344-348 before:

    function searchEventHandler(e){
    e.preventDefault();
    const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile') || document.querySelector('#search');
    let searchTerm = input ? input.value : '';

    Lines 344-348 after removing document.querySelector('#search'):

    function searchEventHandler(e){
    e.preventDefault();
    const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile');
    let searchTerm = input ? input.value : '';

    Lines 376-380 before:

    function searchCloseEventHandler(e){
    e.preventDefault();
    const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile') || document.querySelector('#search');
    if (input) input.value="";
}

    Lines 376-380 after removing document.querySelector('#search'):

    function searchCloseEventHandler(e){
    e.preventDefault();
    const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile');
    if (input) input.value="";
}

  • After listing implementation details, include an action item to test and verify that the changes still work by performing a search in both mobile and desktop views on the Projects and Projects-Check pages

  • Ensure your issue labels match this parent ER (with the exception of Issue Making: Level 1 and ER)

  • Once the overall issue has been drafted, in the sidebar under Relationships, add this ER as a parent to your issue

  • Review and if ready, apply the ready for merge team label

Lenguaje dominante
JavaScript
Estrellas
364
Forks
873
Merge medio
4 d 23 h
PR fusionados (30 d)
11

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 hackforla/website

Todos los issues de hackforla/website

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.