Display Panel always shows "Loading Route Information..." about vscode-laravel-artisan HOT 6 CLOSED

When I run that command in the terminal it takes a while. How long does it take for you to manually run the command artisan route:list --json?

from vscode-laravel-artisan.

thanks for the quick reply.
takes about a second running in the terminal. a little bit longer to see json in the output panel when i invoke the command with the extension.
the video is a little misleading. i've left those display panels open for extended periods of time (10 mins or so) and the display doesn't update.

from vscode-laravel-artisan.

This behavior is really annoying, especially when checking routes, as it keeps repeating to update the real-time listing.

I investigated, and the problem is in the Common.js at:

This line of code forces the display of the output panel/channel for any message, and I believe the correct behavior should be to only open the panel for error messages (as it happens a few lines below) or something relevant to the command we are executing.

I made a pull request removing this line of code. But in my opinion, this option could be configurable if displaying logs is really important for the extension.

from vscode-laravel-artisan.

I just realized that this issue has nothing to do with the pull request I made, which only fixes the unnecessary display and focus gain of the output panel. Please disregard my previous message.

from vscode-laravel-artisan.

Here is a temporary workaround:

Modify the route/List file to the following:

this.subscription = this.observable.subscribe();
setTimeout(() => this.subscription.unsubscribe(), 2000); // add this line

Change the default observer time from 5000ms to 1000ms.This gives enough time to load the routes and will run php artisan route:list only once or twice before the subscription is cancelled by the timeout handler.

Also, if you don't like the Laravel Artisan panel from popping up, comment the outputConsole.show() in utils/Output.

Effectly, this workaround requires you to manually change the extension.
This is not the proper way to fix the undesirable behavior, but it does work.

from vscode-laravel-artisan.

Marking issue as stale since there has'nt been any activity recently.

from vscode-laravel-artisan.