Is there a way to define a Guard instead of binding Authenticatable class?
Long story short, my default Authenticatable class resolves guard that I use on the frontend, not in my filament panel.
And I need to define a guard that will be used in exports.
But I dont want to bind to AUthenticable class because I dont want to change all the auth() calls in the frontend.
Am I making sense, or maybe I'm missing some info?
What if I have multiple panels? How should that resolve?
1 Reply
I can see that when I use the
polymorphic user feature my user still resolves from the default guard, so what is the point of having this?
