Closed jmanuel1 closed 9 months ago
I think this is definitely a Pulsar bug. The command palette scores commands by the total match score of the display name, and description. Which means the description might not match with the query at all. But, when rendering the results, highlightMatchesInElement
is called with the command description and the query in createDescription
, and highlightMatchesInElement
assumes that the description will fuzzy match the query. But it might not, in which case atom.ui.fuzzyMatcher.match
returns undefined.
The reason why the typescript package is involved is that the typescript:build
command has "Compile all files in project related to current active text editor" as a description, which doesn't contain "typescript."
Thanks a lot for investigating this! I'll see if I can get to it tomorrow or Friday.
Thanks a lot for investigating this, @savetheclocktower. A subtle bug and a devops issue in this single issue, but also an easy approve for the fix (for now - I agree that we need to fix that on fuzzaldrin, but well, C++ code being converted to JS is always harder to fix).
Thanks in advance for your bug report!
What happened?
Inputting certain terms into the command palette crashes it and makes it unusable.
Pulsar version
1.113.0
Which OS does this happen on?
🪟 Windows
OS details
Windows 11
Which CPU architecture are you running this on?
x86_64/AMD64
What steps are needed to reproduce this?
Reproduction steps:
An error will be thrown with a stack trace like:
The palette will no longer accept keystrokes, and once you close it, you won't be able to open it again without restarting Pulsar.
Additional Information:
atom-typescript
. Not sure if this is a Pulsar bug.atom-typescript
's activation is deferred; when I activate it and search for a prefix of "typescript" in the command palette, the error occurs