Question about custom item types

[titantwentyone]

Thanks for the package! I was wanting to integrate this with a Post model however I am little unclear on how this is achieved, I've assumed that FilamentNavigation::addItemType is to be used in the boot method of my AppServiceProvider. This gets me so far but I get console errors using the example in the docs:

Alpine Expression Error: Cannot read properties of null (reading 'post_id')

I'm unsure what post_id refers to here in terms of my model (if anything - I assume this used to populate the filed name within data), which, for simplicity's sake, just has id, title and content. (I tried id as well with the same result.). Is there another step needed?

[ryangjchandler]

@titantwentyone Could you share the code that you're trying please?

[titantwentyone]

FilamentNavigation::addItemType('Post link', [
    Select::make('post_id')
        ->searchable()
        ->options(function () {
            return Post::pluck('title', 'id');
        })
]);

The same example used in the docs.

I found that if you remove searchable() everything is fine. Obviously having this would be great though.

[ryangjchandler]

This might be an issue with recent changes to searchable selects. I don't test the plugin with every release of Filament but will try this out within the next day or two when I have some time.

[grahammtbr]

Similar issue here, having Post/post_id as the second addItemType, the options don't load and I can't search for any posts (only on the post itme, Page item works as expected). Removing searchable from posts fixes it. If I remove my Page type, and have have Post as my only custom item type, the post options show up (with searchable) and it does work, but I do get an Alpine error in the console.

Okay, scratch that. I created a new navigation, and no resources work. I get the Alpine error,
Alpine Expression Error: Cannot read properties of null (reading 'xxxx_id')

Ran updates on composer and npm, flushed everything, etc...

[ryangjchandler]

Okay. This is likely an incompatibility with latest Filament releases. I'll have to take some time to look into it. Sorry!