Request for Enhancement: Adding Direct Link to Code Editor Feature in Laravel Telescope

[fh32000]

Dear [Library Team/Developers],

I hope this message finds you well. I'm writing to you as a user and advocate of Laravel Telescope, a fantastic tool that greatly enhances the debugging experience for Laravel developers. I truly appreciate the effort and dedication that has gone into developing and maintaining this invaluable resource.

I wanted to bring to your attention a feature that I believe would significantly enhance the usability and productivity of Laravel Telescope: the addition of a direct link to code editor functionality. This feature would allow developers to seamlessly navigate from Telescope's interface to their code editor, making debugging and troubleshooting even more efficient.

A similar feature is available in another popular debugging tool, Spatie Ignition. Ignition provides users with the ability to configure their preferred code editor through settings in the configuration file, along with options for specifying remote and local sites paths. Here's an example snippet from Ignition's configuration file:

/*
|--------------------------------------------------------------------------
| Editor
|--------------------------------------------------------------------------
|
| Choose your preferred editor to use when clicking any edit button.
|
| Supported: "phpstorm", "vscode", "vscode-insiders", "textmate", "emacs",
|            "sublime", "atom", "nova", "macvim", "idea", "netbeans",
|            "xdebug", "phpstorm-remote"
|
*/

'editor' => env('IGNITION_EDITOR', 'phpstorm'),

'remote_sites_path' => env('IGNITION_REMOTE_SITES_PATH', base_path()),
'local_sites_path' => env('IGNITION_LOCAL_SITES_PATH', ''),

By introducing a similar feature in Laravel Telescope, users would have the flexibility to choose their preferred code editor and easily navigate to the relevant code when debugging requests or exceptions.

I believe this addition would greatly benefit the Laravel community and further solidify Telescope's position as an indispensable tool for Laravel developers. Moreover, the ability to configure the editor and paths via the configuration file would provide users with the necessary flexibility to tailor Telescope to their specific workflows.

I understand that implementing this feature may require time and resources, but I believe the long-term benefits would outweigh the initial investment. I would be more than happy to contribute to the development effort in any way I can, whether it be through testing, documentation, or code contributions.

Thank you for considering this request. I look forward to hearing your thoughts on this matter and eagerly await the possibility of seeing this feature added to Laravel Telescope.

Warm regards,

[@fh32000]

[driesvints]

Thanks. As you can see from the linked PR, we currently have no plans for this, sorry.