Skip to content

Cache already seen entries #4

@Subtixx

Description

@Subtixx

Currently, the extension does not cache entries that have already been seen. This results in repeated processing of the same entries, which can lead to performance inefficiencies.

Steps to Reproduce

  • Perform a search using the ulauncher extension.
  • Observe the entries returned by the KDE baloo indexing service.
    Note that previously seen entries are processed again.

Expected Outcome

Previously seen entries should be cached to avoid reprocessing and improve performance.

Actual Outcome

Previously seen entries are not cached, leading to redundant processing.

Possible Solution

Implement a caching mechanism to store and reuse entries that have already been processed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions