Thanks!

@ifox it's supposed to pick up the filter() method if I have one of those traits on my model?

I've tried a few variations on the model without success

Unless these are controller traits

do you mean repository?

the filter method is to be implemented from the repository class of your module, under App/Repositories

Sorry, that's what I meant the first bit, repository. It doesn't seem to be firing the methof

Actually, it is --- my dd() call fires, but none of the examples do

Aha, the structure is different than the example

Still no luck, but it's something for me to work off of in the morning. Thanks!

examples there probably need a review and docs update, let me know what you find

Aha, it's because they're not normal relations, they're in the relations table.

This is all starting to make sense with the computed field

oh ok, so you select one artist on albums, or multiple albums in one artist? In any case I would recommend to setup a proper relationship and database structure for such relationship. In the first case, a belongsTo on the album model, with a foreign key artist_id. In the album repository you'd use

$browsers

instead of

$relatedBrowsers

.

Hi, @ifox. Yesterday, I add comment to this topic https://discord.com/channels/811936425858695198/989478663865114664. Could you please give some feedback. Thanks

Hey guys, some questions on the nested module, I pass the parents in formData of the Controller, and I get this. Is there any way to allow searching in the parent page select component and what is the "Go to page" select for?

hey @thingasd searching in there, not at the moment, but that could be added. Go to page is meant to be a quick way to move from one sibling child to another, it also has go to previous and go to next links if you provide the data.

You mean like

protected $browsers = ['artist'];

in the album repository?

yes

I ask because oddly that's what I have

oh, so you do have a artist_id column in your albums table then?

Yes

This is why I was confused yesterday, I was unaware it was using the relations table instead of the regular relation

I'm not sure I'm following why it'd use the relations table, in what context do you mean? Do you actually see rows in the

related

table for the album->artist relationship?

Yes, it looks like all of them are in there

I'm going to try wiping my local DB and running the import again, see if it still goes to the related table

are you doing something in

afterSave

?

Nothing like that

import? are you programmatically creating the records?