How to show error messages when you make a custom operation

[christmex]

Hi guys, this week I'm making a custom operation and I use this article as my reference
https://backpackforlaravel.com/articles/tutorials/how-to-create-a-custom-operation-that-uses-backpack-fields

it's all good, I did all of the steps correctly, but after that, I got some problems, after validation, the error messages didn't show up to the user, so I'm baffled, I'm trying to compare my file with another operation also the blade form, it's all good, nothing was wrong but it's still not showing the error messages, but today I think I figure it out, how to show the errors, I add 2 lines inside my setupYourOperationDefaults(), here are the details

    protected function setupYourOperationDefaults()
    {
        CRUD::allowAccess('yourOperation');

        CRUD::operation('yourOperation', function () {
            CRUD::loadDefaultOperationSettingsFromConfig();
            [+] $this->crud->enableInlineErrors();
            [+] $this->crud->enableGroupedErrors();
        });

        ...
    }

Please let me know did I missing something. or this is not the way how to show the errors, thank you guys, I hope I can help someone with this. Thanks.

[tabacitu]

Ooooh! That might actually be needed, yes. Thanks!

@karandatwani92 do you think we need to add that to the article too?

[karandatwani92]

IDK @tabacitu, I just re-checked by following the tutorial step by step. I find it working without calling above methods.

What do you think?

[pxpm]

Hey guys, I know this is a bit old, I was just doing some late checking on the issues to get up-to-date.

This indeed works if you follow the tutorial step by step. 👍

I think what @christmex is missing is the step to duplicate the config file.

Copying the create config into your customOperation config file, should get you this by default:

 // How would you like the validation errors to be shown?
    'groupedErrors' => true,
    'inlineErrors'  => true,

Anyway this setting is a little bit hidden, a not properly documented on Backpack side.

I say that we should probably add this to our documentation, but take advantage of it never been documented before and don't document the CrudPanel functions (enableInlineErrors() and enableGroupedErrors()) like @christmex suggested, but use the CRUD::setOperationSetting('groupedErrors/inlineErrors', true/false) to document it.

This settings belong to a future FormComponent and not to the CrudPanel object, so let's not use those functions to document it so that we can easily deprecated them in the future if/when needed.

What do your think @karandatwani92 ?

[christmex]

Thank you so much for your feedback @pxpm , that's helpful, how could I miss that 😣😓

[pxpm]

I don't think it's your fault for missing that. I think it's totally fine that you missed it, we didn't properly document it 🙏

We aren't doing a good job at the moment to have a "clean" way for developer to create custom operations that uses fields in a form. Asking a developer to copy a config from other operation because "he needs some of the configs" is not a valid thing to do in my opinion, it's cheating the game until we have implemented a proper solution.

We are aware of it, and already have on the roadmap a "simple way for developers to create custom operations with forms".

Thank you for your feedback and raising those questions, it helps us to understand developer pain points, bad documentation etc.

Every question is important, even if silly!

Cheers, have a nice weekend! 🥂

[jcastroa87]

I'm closing this issue due to inactivity. If you need further assistance or have additional questions, feel free to reopen this issue or create a new one. We're here to help!