fix: Use navigation.group configuration in MailResource

[HelgeSverre]

Summary

• Fixes the MailResource to use the filament-mails.navigation.group configuration option
• Previously the navigation group was hardcoded to __('Emails') ignoring the config
• Now reads from config with a fallback to the previous default value

Details

The issue was in src/Resources/MailResource.php:61 where getNavigationGroup() returned a hardcoded value instead of checking the configuration.

Before:

public static function getNavigationGroup(): ?string
{
    return __('Emails');
}

After:

public static function getNavigationGroup(): ?string
{
    return config('filament-mails.navigation.group', __('Emails'));
}

Test plan

• Verified the configuration option exists in config/filament-mails.php
• Confirmed EventResource and SuppressionResource already properly reference MailResource's navigation group
• Change maintains backward compatibility with fallback to previous default

Closes #58

🤖 Generated with Claude Code

[Baspa]

Fixed in v3.0.4, thanks @HelgeSverre!

[arshaviras]

Hi @markvaneijk , this method not works!

public static function getNavigationGroup(): ?string
    {
        return config('filament-mails.navigation.group', __('Emails'));
    }

In Laravel, config('key', $default) only uses $default if the key is missing - not when it exists and is null.

So config('filament-mails.navigation.group', __('Emails')) resolves to null, which means no group header.

I think you should use like this

public static function getNavigationGroup(): ?string
    {
        return __(config('filament-mails.navigation.group') ?? 'Emails');
    }

If need I can create PR for this.
Thanks

[arshaviras]

@markvaneijk, @Baspa this will not work, it will thrown error - __() helper can't used in config files, but we need to use multilingual key. So my version described above resolves an issue.

'navigation' => [
        'group' => __('Emails'),
        'sort' => 9,
    ],

[markvaneijk]

You are correct @arshaviras, we've released v3.0.6 with a fix for this and added some extra configuration options.