LMMS / LMMS/lmms

Ignoring spaces in effect search

Open
#6,324 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

### Enhancement Summary
If one searches for "Stereo enhancer," show result "StereoEnhancer effect," and if one searches for "StereoMatrix," show result "Stereo Matrix" (by running a search alongside that ignores spaces in results/search expression).
(Also, if possible, rename StereoEnhancer to "Stereo Enhancer" by putting a space in between, see Justification)

#### Justification
I have to consciously remember to keep myself from putting a space between "Stereo" and "Enhancer," or from typing "StereoMatrix" (one word), because both throw no results.
The ability of search to ignore a space in both search listings and search box would be quite useful as a behaviour.
(Additionally it'd be nice if there was a standard for naming effect plugins so there would be consistency in the results. But that's a plus.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by locating LMMS's effect search entry point and tracing how search expressions are matched against effect names; verify the stated Stereo enhancer/StereoEnhancer and StereoMatrix/Stereo Matrix cases, then confirm the existing effect naming and search tests cover the intended behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.