@push to view @stack from service provider

[dillingham]

A way to @push to a @stack from a service provider would enable packages the ability to extend other package's views.

$this->pushStack('jetstream::menu.after', 'package::notification-menu');

Adding hooks before and after specific parts of a UI would make it very extensible so other packages can inject views.

@stack('jetstream::header.before')
@stack('jetstream::header.after')
@stack('jetstream::dropdown.before')
@stack('jetstream::dropdown.after')
@stack('jetstream::profile.before')
@stack('jetstream::profile.after')

Maybe an optional array of views for "use first view":

$this->pushStack('jetstream::menu.after', ['notification-menu', 'package::notification-menu']);

You could even use this approach to populate vue components:

<script id="vue-component">
    @stack('package::vue-component.before')
    @include('package::vue-component')
    @stack('package::vue-component.after')
</script>

const VueComponent = {
  template: '#vue-component'
  // ...
}

---

Example Jetstream package scenarios:

• oAuth Package: [2.x] Socialite Support jetstream#444
• Notification Profile Preferences
• Notification Bell Dropdown
• Billing profile settings
• GDPR export / settings

Would allow Spark to be a "Premium Jetstream Package"

[dillingham]

@driesvints brought up a good point about unpredictable ordering in the socialite support PR.

A method to optionally control the order of stacks would be nice:

$this->pushStackOrder('jetstream::menu.after', [
    'package-one::notification-menu',
    'package-two::support-button',
]);

[dillingham]

Maybe if a package includes views you don't want:

$this->pushStackIgnore('jetstream::menu.after', 'package-three::unwanted-view');