bayleeadamoss/zazu

Zazu plugin is activating, but Zazu doesn't show plugin output

Open

#322 opened on Jul 13, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (2,093 stars) (186 forks)batch import
bughelp wanted

Description

Expected Behavior

Zazu should display plugin results correctly.

Actual Behavior

Plugins activate properly, but their results are not rendered by Zazu.

Sseems to me that Zazu goes to fallback mode and the actual plugin's output is not shown. Only the fallback (file-search) output is rendered.

Steps to reproduce the behavior

  • install Zazu for windows via zazu-Setup-0.5.2.exe
  • install a plugin, say "zazu-ip-address" from https://github.com/blakek/zazu-ip-address
  • try to activate the above plugin (Open Zazu and type ip)
  • the plugin generates proper output, but it doesn't show up in Zazu.
  • Zazu falls back to file search for the given text, ip

See screenshot with plugin logs: https://imgur.com/XYCnu9M

This erroneous behavior is not limited to the above plugin, it also happens for other plugins too (e.g. the giphy plugin also doesn't work as expected).

Versions

  • Zazu: 0.5.2
  • OS: Windows 10 Pro, 64 bit

Please, include a link to gist of most applicable ~/.zazu/log/ file.

https://gist.github.com/nonbeing/48375a6fbc27a80ad6161acf3a441985

Relevant snippet from logs:

{"results":[{"icon":"fa-globe","title":"Internal IP: 192.168.1.6","subtitle":"(Select to copy to the clipboard)","value":"192.168.1.6"},{"icon":"fa-globe","title":"Public IP: 185.203.122.9","subtitle":"(Select to copy to the clipboard)","value":"185.203.122.9"}],"plugin":"blakek/zazu-ip-address","block":"cjjjp9wau0000lor38cl4rrdf","level":"info","message":"Script Results","timestamp":"2018-07-13T08:08:28.407Z"}

NOTE : the actual value of public IP in the logs has been changed. Have verified that the plugin works correctly and the logs do have the correct public IP.

Contributor guide

Tech stack
javascript
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic JavaScriptUnderstanding of plugin systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by examining the rendering logic in Zazu, particularly how plugin results are displayed and the fallback mechanism. Look at the renderer or plugin handler files for any condition that might cause the fallback to override plugin output. The logs show correct plugin results, so the issue likely lies in how Zazu decides to show fallback instead. Check the issue comments for any hints from maintainers.