Batman Comments - Answer Overflow

Topics

Batman

•Created by Batman on 4/2/2025 in #❓┊help

Select::make('category_id') VS. Select::make('Category')

Yes, as stated above, I am using ‘category_id’ as in the documentation. But ran across this and wondered why it worked and just stopped. It was a tutorial that I had previously went through that had some things I remember doing and revisited!the code and project. Was looking through it yesterday and ran the project and all was working. Started it up today and it didn’t work. So it bothered me as to why.

17 replies

•Created by Batman on 4/2/2025 in #❓┊help

Select::make('category_id') VS. Select::make('Category')

Yeah, that particular is V3, don’t remember the minor revision or what version of laravel they were using then though.

17 replies

•Created by Batman on 4/2/2025 in #❓┊help

Select::make('category_id') VS. Select::make('Category')

I’ll have to check on the case sensitivity. And yes, I agree, better to be explicit. Also just one of those things that I wanted to get to the bottom of. If it wouldn’t have worked to begin with I wouldn’t have thought twice about it, but one of those, worked yesterday, but not today, so what’s going on type of things.

17 replies

•Created by Batman on 4/2/2025 in #❓┊help

Select::make('category_id') VS. Select::make('Category')

Correct, I understand that’s the correct way to do it. What I’m trying to fully understand is why using ‘category’ works (resolves) the relationship correctly when updating the field, but not when creating. It’s not an issue as I am using the category_id. But it is something I ran across and was bugging me why it was working, then just stopped. So, I was trying to find more clarification on why it seems to be resolving the relation on both creating and updating, and now it’s only resolving only on updating.

17 replies

•Created by Batman on 4/2/2025 in #❓┊help

Select::make('category_id') VS. Select::make('Category')

It’s an issue of not properly creating the relation on creation, not trying to resolve a relation on null. It used to properly create the model entry (correctly inserting the value into ‘category_id’) but doesn’t anymore. It now looks for a field called ‘Category’ instead of using the relationship. This only happens on create, not update.

17 replies

•Created by Batman on 3/28/2025 in #❓┊help

Populate Select with only a select subset of an enum

@Ash Thank you! Keywords I was searching did not bring up yours unfortunately.

7 replies

•Created by Batman on 3/28/2025 in #❓┊help

Populate Select with only a select subset of an enum

public static function getStatusSelectBuilder(?Article $record, string $operation = 'create'): array
    {
        $allowedStatus = [];

        if ($operation === 'edit') {
            $allowedStatus[] = $record->status;
        }

        if (Auth::user()->can('draft', Article::class)) {
            $allowedStatus[] = ArticleStatus::DRAFT;
        }

        if (Auth::user()->can('ready-for-review', Article::class)) {
            $allowedStatus[] = ArticleStatus::READY_FOR_REVIEW;
        }

        if (Auth::user()->can('pending-review', Article::class)) {
            $allowedStatus[] = ArticleStatus::PENDING_REVIEW;
        }

        if (Auth::user()->can('approve', Article::class)) {
            $allowedStatus[] = ArticleStatus::APPROVED;
        }

        if (Auth::user()->can('reject', Article::class)) {
            $allowedStatus[] = ArticleStatus::REJECTED;
        }

        if (Auth::user()->can('archive', Article::class)) {
            $allowedStatus[] = ArticleStatus::ARCHIVED;
        }

        return $allowedStatus;
    }

public static function getStatusSelectBuilder(?Article $record, string $operation = 'create'): array
    {
        $allowedStatus = [];

        if ($operation === 'edit') {
            $allowedStatus[] = $record->status;
        }

        if (Auth::user()->can('draft', Article::class)) {
            $allowedStatus[] = ArticleStatus::DRAFT;
        }

        if (Auth::user()->can('ready-for-review', Article::class)) {
            $allowedStatus[] = ArticleStatus::READY_FOR_REVIEW;
        }

        if (Auth::user()->can('pending-review', Article::class)) {
            $allowedStatus[] = ArticleStatus::PENDING_REVIEW;
        }

        if (Auth::user()->can('approve', Article::class)) {
            $allowedStatus[] = ArticleStatus::APPROVED;
        }

        if (Auth::user()->can('reject', Article::class)) {
            $allowedStatus[] = ArticleStatus::REJECTED;
        }

        if (Auth::user()->can('archive', Article::class)) {
            $allowedStatus[] = ArticleStatus::ARCHIVED;
        }

        return $allowedStatus;
    }

7 replies

•Created by Batman on 3/27/2025 in #❓┊help

Markdown Toolbar Buttons

While this does work, we are talking about users. I guess I ll have to put up instructions, but that defeats the purpose of a wysig in my opinion.

9 replies

•Created by Batman on 3/27/2025 in #❓┊help

Markdown Toolbar Buttons

It works fine if you edit it and know markdown, just would like buttons for those that don't.

9 replies

•Created by Batman on 3/27/2025 in #❓┊help

Markdown Toolbar Buttons

I also see some older questions on preview for v3 and it appears that it was set as not planned in github. Is the pboivin/filament-peek:"^2.0" still the best alternative to in editor preview?

9 replies

•Created by Batman on 3/27/2025 in #❓┊help

Markdown Toolbar Buttons

Articles to be submitted/created in markdown. Would like to have the option of H2 and H3 as sub headings.

9 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

So, if I uncomment $this->withoutVite(); in TestCase->setup() everything works correctly. Not sure why that would interfere, but there is a difference.

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

Yeah, I'm seeing some differences between the two repositories which I'm sure will help some of these anomalies. I'm still trying to figure out why ->disabled(fn () => true) isn't returning as disabled.

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

I'm trying to make sure something didn't get out of sync between dev and testing database

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

That is why I was wondering if there was something I didn't have correct, like waiting for the form to render first so the functions were able to execute.

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

I'm having the same issue with testing readonly settings also.

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

No description

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

I tried both, even if I only evaluate

->assertFormFieldIsDisabled('email')

->assertFormFieldIsDisabled('email')

it fails

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

The anonymous functions are not being evaluated before the form test. This still fails:

->disabled(fn () => true)

->disabled(fn () => true)

29 replies

•Created by Batman on 3/24/2025 in #❓┊help

Are anonymous functions evaluated before ->assertFormField*?

No, there are only single roles in this application.

29 replies