`unknown directive` on custom blade directives

[angeljqv]

• 8

  In my previous issue you added the functionality to autocomplete the blade directives(custom/3rd party), in version 2, it still works but it marks them as unknown directive, but if they are added for autocompletion they should be known, or am i missing something? This leaves too many messages in all my documents, it's harder to focus on the messages that really matter.

[haidubogdan]

It's strange if the blade is added in autocompletion It should be considered a custom directive.

You can try to re-add the service provider class where you define the blade directives with Project -> Properties -> Laravel Blade -> Custom Directives

---

The current system is designed that on Ctrl+Click over a custom directive to go the the Service Provider Class where the custom directive was defined.

[angeljqv]

From spatie/laravel-permission/src/PermissionServiceProvider.php#L129-L138

I already tried to add the service provider again, I also tried to clear the entire netbeans cache, I am using Netbeans 19

---

The current system is designed that on Ctrl+Click over a custom directive to go the the Service Provider Class where the custom directive was defined.

I didn't know it, Ctrl + Click does exactly what you say, open the service provider

---

Maybe it is not possible, but what about this idea

It doesn't work with relative paths Files with custom directives always are inside project root path, so, we can use relative paths instead of absolute paths(same with views path)

After that, what if instead of saving in private.properties it save it in project.properties, so it could be on the repository tree, everyone with the plugin could use custom directives autocompletion automatically

[angeljqv]

There is no way to disable that message

[angeljqv]

I updated to a newer netbeans, the message disappeared, but there is a strange underline

[haidubogdan]

cool, this is just to have a soft identification that it is a custom directive.

[angeljqv]

I have these 3 custom directives

@card like no blade directive, @cardTitle strange underline, and @endcard is fine

If i remove @cardTitle args, no more blade directive

If i add (), @card starts working, maybe related to #37

---

[parallels999]

@card like no blade directive, @cardTitle strange underline, and @endcard is fine If i remove @cardTitle args, no more blade directive If i add ( ), @card starts working, maybe related to https://github.com/haidubogdan/netbeans-php-blade-plugin/issues/37

+1

[haidubogdan]

For the moment I've prepared a pre-release to recognize custom directives whiteout arguments

https://github.com/haidubogdan/netbeans-php-blade-plugin/releases/tag/nb180-v.2.0.7-pre .

There are some things which are still work in progress

[haidubogdan]

Closing the ticket. From v.2.1.21 there is the option to disable these types of warnings :

Editor -> Hints -> Language Blade :

[josevv28]

It doesn't work with relative paths Files with custom directives always are inside project root path, so, we can use relative paths instead of absolute paths(same with views path)

After that, what if instead of saving in private.properties it save it in project.properties, so it could be on the repository tree, everyone with the plugin could use custom directives autocompletion automatically

Sounds like a great idea

[angeljqv]

Hi @haidubogdan, the problem is back, There should not be any type of tests to prevent already solved bugs from returning.

@card
  @cardTitle([

---

I have these 3 custom directives

@card like no blade directive, @cardTitle strange underline, and @endcard is fine

If i remove @cardTitle args, no more blade directive

If i add (), @card starts working, maybe related to #37

[haidubogdan]

Hi, you are right, some tests should be implemented in the future.

[angeljqv]

It works again, thanks