Lukas Frey

The package was created for a project with multi tenancy, where I use it on a daily basis. Do you use filaments multi tenancy or some 3rd party package?

A possible fix would be to provide our own Translatable implementation just like we do in Nested Resources, but then if these two packages would be used together, a collision...

Hi, I use my own language switch, so I never run into this issue. A PR to fix it is more than welcome. Otherwise, I'm working on v2 where due...

You should only remove them from the child nested resources, not the root one.

Hi Kevin, I'm not sure I like that approach, but since I have no better solution right now, I'd be open to accept the PR. But I think I prefer...

@iAmKevinMcKee Yes, exactly. Except I don't think there's a need to ignore the `icon` set in the front matter of each documentation. If you only want to have an icon...

@z4yed You need to implement the `$relationship` property. I guess in your case it will be something like: ```php protected static string $relationship = 'lessons'; ```

> This worked. However, when I am in view/edit page of any lesson, the `root` navigation section `Courses` is not active (highlighted). Please see attached image. > >  Great...

Sorry, I think I used the wrong issue template. I can not change the labels back to normal though.

> I studied the code and found that: this.$dispatch("open-modal", {id: t}) cannot trigger window.open-modal, which causes x-on:open-modal.window to not trigger. If I replace it with: > This kinda works, but...