[Bug]: Search Not Working

[jonchen727]

Describe the bug

Search does not after upgrading to 2.1.0.

To reproduce

1. Enter anything into search

Version

2.1.0

OS

macOS

Validations

• Follow our Code of Conduct
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.

[heliomcp]

Related with my issue closed (#35).

[antonreshetov]

Is there any sequence of actions leading to this bug? Because I can't reproduce this bug.

[github-actions]

Hello @jonchen727. Please describe in detail the sequence of actions that leads to the bug. Add screenshots of errors from the console. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[lt-laurap]

Same problem here.
It's easier to notice when you try to search within a Folder, you will be redirected to the All Snippets section.

[antonreshetov]

@lt-laurap redirecting to All Snippets during a search is normal behavior, because the search is performed on all snippets, not on a selected folder.

[jonchen727]

Issue still present in v2.2.0
Steps to reproduce.

1. Search for kubectl, results are returned do not have kubectl in the snippet.

Redid the search again and looks like kubectl highlights nordvpn and pretty much every 7 character combination

Some examples that are shorter work such as searching auth

[antonreshetov]

@jonchen727 Still can't reproduce the bug. Maybe the db.json is corrupted?

Search is a very simple function:

massCode/src/renderer/store/snippets.ts

Line 271 in c486fbf

search (query: string) {

Open db.json in the editor and look in this snippet in content[].value because according to the error in the console value is missing

[jonchen727]

@antonreshetov
I found the issue, there was one snippet with a fragment with value null and the other fragment had a value. Now search works as intended, however there is another issue I saw.

When doing a search and the first fragment does not contain the search term, while the others do there, a weird highlighting occurs when you go into the fragment that contains the search term then to a different snippet, then back to the default fragment.

[antonreshetov]

@jonchen727 That's a good thing. Then this Issue can be closed.

[heliomcp]

@antonreshetov I found the issue, there was one snippet with a fragment with value null and the other fragment had a value. Now search works as intended, however there is another issue I saw.

When doing a search and the first fragment does not contain the search term, while the others do there, a weird highlighting occurs when you go into the fragment that contains the search term then to a different snippet, then back to the default fragment.

Thank you, @jonchen727

@antonreshetov maybe there is something in database migration that is not working properly for this behavior?