Today's work was a small piece of UX that's easy to underestimate: making an admin "browser" page scope itself to whatever you clicked to get there. The setup is one I keep running into — you have a list of connectors (think AD/LDAP directory connections), and each connector has its own users and its own groups. The old flow dumped you into a generic Users browser and made you re-pick the connector from a dropdown. Annoying. You already told the app which connector you cared about by clicking its row.
The fix is the kind of thing Livewire makes almost too easy, so I want to slow down and talk about why it works and where the edge cases hide.
The core idea: a URL-bound property
The whole feature hinges on one attribute. In Livewire, you can bind a public property straight to a query-string parameter:
use Livewire\Attributes\Url;
