From what I can tell, it seems that the @props directive that is used by Laravel to make Blade Components (here) isn't supported by default at the moment.
Since this is a Laravel-supported directive, I think it would make sense to add into the plugin. Right now, I can get around it fairly easily by using the vim configurations for custom directive (thanks for adding that, by the way–it's super helpful), but it would be nice to not have to worry about adding @props to the list myself.
I'm happy to take a stab at this issue, but I'm going out of town shortly for about a week, so I figured that I'd go ahead and open an Issue in case anyone wanted to work on this while I'm away from my computer.
Also, as always, if this isn't an issue, please let me know!
Thanks for supporting this plugin! It's a huge part of my vim workflow for Laravel development 👍🏻
From what I can tell, it seems that the
@propsdirective that is used by Laravel to make Blade Components (here) isn't supported by default at the moment.Since this is a Laravel-supported directive, I think it would make sense to add into the plugin. Right now, I can get around it fairly easily by using the vim configurations for custom directive (thanks for adding that, by the way–it's super helpful), but it would be nice to not have to worry about adding
@propsto the list myself.I'm happy to take a stab at this issue, but I'm going out of town shortly for about a week, so I figured that I'd go ahead and open an Issue in case anyone wanted to work on this while I'm away from my computer.
Also, as always, if this isn't an issue, please let me know!
Thanks for supporting this plugin! It's a huge part of my vim workflow for Laravel development 👍🏻