Jetstream 4.x defaultApiTokenPermissions ability format conflicts with UI comma-separated input
This question examines the serialization boundary between Jetstream's defaultApiTokenPermissions configuration array and the ApiTokenManager Livewire component when creating new personal access tokens. The configuration accepts ability names as strings, while the UI serializes input as comma-separated values for storage in the abilities JSON column on the pe
laraveljetstream