Noah Frederick

Thanks for the suggestion. Note that navigation to class/interface/trait source files is already supported by `(composer-find)` and insertion of `use` statements by `(composer-use)`. This is documented in `:help composer-maps`. The...

> No modification of files in the project's vendor needed. You wrote: > Class map is written into file `vendor/composer/autoload_static.php` This has the consequence of subsequent changes not being picked...

Very cool. > Maybe the cursor has to be returned back after calling `composer#namespace#use`. Yes, this function (intentionally) moves the cursor to the new `use` statement. What happens if you...

> I wanted to add the `listGreppedClasses.php` script into the plugin Since this doesn't require PHP, I'd rather rewrite it in Vim Script. If you want to try yourself, look...

@adriaanzon Hey, that's pretty clean. I'd still prefer to invert the relationship so that we have a generic `composer#namespace#classes()` (or something like that) that can be reused elsewhere, and to...

Thanks for the report. I'm not familiar with vim-airline and which highlight groups it pulls from the color scheme. Given that I don't use vim-airline, I'm probably not going to...

@khughitt > some other colorschemes which behave well If you know of one that relies on the value of `'background'`, please link it here. I suspect that `:set background` simply...

Thanks! This addition is welcome, but the proposed code change has a couple problems: 1. It overwrites the original function, so we've lost support for `trans()` and `trans_choice()`. 2. The...

Do you want to try adding test coverage? It would involve using [vader.vim](https://github.com/junegunn/vader.vim) to make assertions about the output of `laravel#goto#filetype_php()` and `laravel#goto#filetype_blade()` when the cursor is on different snippets...

The plug-in is only activated for buffers that are actual files in a Laravel project (and it doesn't care about your current working directory), whereas `n` creates a new, empty...