move blade directives after resolving

[bmichotte]

By using Blade::directive from your register method seems to force blade to fire its resolving, causing other packages which load their directives afterResolving to fail.

See spatie/laravel-permission#458, albertcht/invisible-recaptcha#41 and related issues

[drbyte]

👍
While I haven't encountered this clash when using both laravel-impersonate and laravel-permission, I've seen invisible-recaptcha cause troubles for the reason explained here.

Definitely appears to be safest to wrap all Blade directive assignments into the afterResolving of blade.compiler as this PR proposes.

[MarceauKa]

Thank you!

[Treggats]

@MarceauKa can you create a release for this?

I've had laravel-permission blade directives show up and by updating this package to "dev-master" they were fixed.

[bmichotte]

@MarceauKa any chance you'd tag a new release soon or at least some eta ?

[bmichotte]

As a workaround while we are all waiting for release, you can use this in your composer.json

"require": {
      "lab404/laravel-impersonate": "dev-master",
},
"config": {
    "preferred-install": {
      "lab404/laravel-impersonate": "source",
      "*": "dist"
    }
  }

[drbyte]

v1.2.2 has now been tagged, and includes this fix.