You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phpcs has stopped showing the quick panel as well as errors in the gutter and status bar. This seemed to have happened fairly recently but I'm not sure when it started. I only realized it today when I began to wonder if I'd developed code-formatting superpowers because I hadn't seen any errors in a while.
I'm a Linux user and thought this might be related to #115, but my version of phpcs is 6.5.1 and I'm still getting nothing, so it must be a different issue.
Phpcs works in the console. Here's the relevant output:
[Phpcs] Linter found 0 errors
[Phpcs] Sniffer found 1 errors
Traceback (most recent call last):
File "phpcs in /home/autumn/.config/sublime-text-3/Installed Packages/Phpcs.sublime-package", line 483, in generate
File "/opt/sublime_text_3/sublime.py", line 861, in add_regions
sublime_api.view_add_regions(self.view_id, key, regions, scope, icon, flags)
TypeError: String required
@autumnlansing Good spot. Figured out the issue from the stack trace. It's related to GH-114, which allowed you to stylise the icon in the gutter. I only tested when phpcs_icon_scope_color was defined.. But this may not always be the cause, which meant the preference was None and not a string. I now define the default and pushed up 6.5.2.
Apologies about this issue, and thanks for raising.
Phpcs has stopped showing the quick panel as well as errors in the gutter and status bar. This seemed to have happened fairly recently but I'm not sure when it started. I only realized it today when I began to wonder if I'd developed code-formatting superpowers because I hadn't seen any errors in a while.
I'm a Linux user and thought this might be related to #115, but my version of phpcs is 6.5.1 and I'm still getting nothing, so it must be a different issue.
Phpcs works in the console. Here's the relevant output:
I'm also seeing this error in the console:
The text was updated successfully, but these errors were encountered: