There is currently no way to get validation errors with Antlers. With Blade you can easily do the following:

@if ($errors->any())     
    <p>There were $errors->count() errors</p> 
    <ul>
        @foreach ($errors->all() as $error)
            <li>{{ $error }}</li>
        @endforeach
    </ul>
@endif

I'm currently using a custom tag to get around this. But I was wondering if you are open to a PR that adds the functionality to this package. It could work like this:

{{ if {livewire:errors} }}
    <p>There were {{ livewire:error_count }} errors</p> 
    <ul>
        {{ livewire:errors }}
            <li>{{ error }}</li>
        {{ livewire:errors }}
    </ul>
{{ /if }}

Is there a way to use pagination like documented here? In Blade you would use {{ $posts->links() }} to render the pagination view? I couldn't figure out a way to do this in Antlers.

The idea of this PR is to make the Statamic context available as public property in your Livewire components. Having the context available can help to reduce the number of properties you have to pass down the component in your view.

Simply add the WithContext trait to your component and you're good to go.

I'm not completely sure, but one possible limitation is probably the reactivity of the context property. If you want to make certain context properties reactive, you'd still have to manually create a new livewire property and mount the context value to it. At least this would reduce the noise in your template.

Another idea could be to do some magic and automatically add all context properties as a livewire property. But this might lead to other issues as well.

Please give feedback on what you think about this idea.

Hey Jonas

Thanks again for this package. I have discovered an issue:

• Use antlers for a component view
• Use Alpine to share state between Alpine and Livewire using @entangle see docs
• See error in console when viewing the component

I guess this due to the use of @ in the template and it breaks something in Antlers, although I'm not sharp enough to know exactly what.

I have made a demo repo that you can clone to see the issue in real life: https://github.com/johncarter-/statamic-antlers-livewire-entangle-error

Sorry I can't fix it.

Redirecting to another page within a Livewire component throws this error:

Jonassiewertsen\Livewire\Tags\Livewire::wildcard(): Return value must be of type string, null returned

You can reproduce this using this code:

public function mount()
{
    return redirect()->to('/');
}

Versions: Statamic 3.2.16 Pro Laravel 8.64.0 PHP 8.0.12 jonassiewertsen/statamic-livewire 2.7.0

Hi,

I'm running into a weird issue and I think it has something to do with statamic-livewire.

What I try to do

I use a slider. When the slider is updated (a new slide is selected) I want the data on the selected slide to be available in Livewire.

What happens

When I emit an event to Livewire, or update an entangled value, the JS of the slider breaks.

What I tried

• Trying different sliders (Swiper & Flickity)
• Trying to use Alpine and Vanille JS
• Trying to emit events using Antlers and Blade
• Trying to use entangle or {{ livewire:this set="" }}

My code

    <div x-data="{flkty: null}" x-init="
        flkty = new Flickity( '.main-carousel', {
            wrapAround: true
        });

        flkty.on('select', function(index) {
            {{ livewire:this set="('dataset', flkty.selectedElement.dataset.test)" }}
        });
    ">

        <div class="main-carousel">
          <div class="w-full" data-test="data 1">Slide 1</div>
          <div class="w-full" data-test="data 2">Slide 2</div>
          <div class="w-full" data-test="data 3">Slide 3</div>
        </div>

    </div>

    <div class="output">
        {{ dataset }}
    </div>

Livewire:

class MyComponent extends Component
{
    
    public $dataset;

    public function render()
    {
        return view('livewire.my-component');
    }
}

Is this the desired effect that when passing an Statamic\Entries\Entry parameter it gets augmented?

On vendor/jonassiewertsen/statamic-livewire/src/Tags/Livewire.php: $parameters->toArray() will convert the Entry to an augmented array. If we replace ->toArray() with ->all() the Entry stays an object.

Here is the output from Ray from line #43:

Let me know if it's a bug and you want me to PR.

I'm using this add on to build a checkout component, which in turn has some nested components (basket view and country/state selector).

The issue is that when the nested component (eg country/state) emits an event that affects the parent component (checkout), the child components get re-rendered. If I rebuild the components in blade rather than antlers this does not happen.

Is this a known issue? Is there a work around?

Hi

I need to perform a filter before using the pagination. But when i do got an error: Method Statamic\Entries\EntryCollection::paginate does not exist.

My code:

    {
            $entries = Entry::query()
            ->where('collection', 'projects')
            ->where('locale', Site::current()->handle)
            ->get()
            ->filter(function ($entry, $key) {
                return $this->filters['categories'] ? (array_intersect($entry->get('categories'), $this->filters['categories'])) : true;
                }
            )
            ->filter(function ($entry, $key) {
                return $this->filters['q'] ?  str_contains($entry->get('title'), $this->filters['q']) : true;
        }
        )->paginate(3);


        return $this->withPagination('entries', $entries);
    }

This works:

protected function entries()
    {
            $entries = Entry::query()
            ->where('collection', 'projects')
            ->where('locale', Site::current()->handle)
            ->paginate(3);


        return $this->withPagination('entries', $entries);
    }

But i need to filter the content beforehand. How can i do this?

Hi, not sure If I'm missing something, or if this is something that can be easily corrected with a changed approach... but wanted to raise it in case it's something that can be resolved in the addon.

I'm using the statamic-livewire addon for a simple Articles/news feed, using the use Jonassiewertsen\Livewire\WithPagination namespace.

When using the pagination, the Statamic {{ updated_at }} variable is changing from 'March 11th, 2022' to: '2022-03-11 06:00:27'.

Anything simple I can do to resolve this? I'm using Antlers for the view, so ideally the solution would be Antlers rather than blade.

Using global Statamic variables with Antlers would be very useful, but since livewire is not persisting private variables through render cycles and setting the global set to a public variable on mount will produce an error I'm not quite sure what the best practice for this would be.

This approach works, but doesn't feel right to me:

public function mount($fallbacks) {
        session(['fallbacks' => $fallbacks]);
}

public function render()
{
    return view('blocks.counter', [
      "fallbacks" => session('fallbacks'),
    ]);
}

An this is how the component is getting called:

{{ livewire:counter :fallbacks="fallbacks" }}

Would be awesome do add some best practice to the readme.

Thanks,

Hi!

I’m trying to bind a deferred model to an input in an antlers template like that:

<input type="text" wire:model.defer="searchTerm" />

Unfortunately this doesn’t work at all. Using it without defer runs like expected.

Does someone has a suggestion what might be wrong?

Thank you :)