Correct the user model configuration key

[gleb-svitelskiy]

WHY

BEFORE - What was wrong? What was happening before this PR?

Fixing this bug.

AFTER - What is happening after this PR?

Fixing this bug.

HOW

How did you achieve that, in technical terms?

I'm using the correct config key.

Is it a breaking change or non-breaking change?

Non-breaking change.

How can we test the before & after?

Try to create a new user with overridden Backpack user model.

[welcome[bot]]

BOOM! Your first PR with us, thank you so much! Someone will take a look at it shortly.

Please keep in mind that:

• if this constitutes a breaking change, it might take quite a while for this to get merged; we try to emulate the Laravel release cycle as much as possible, so developers can upgrade both software once; this means a new big release every ~6 months;
• even if it's a non-breaking change, it might take a few days/weeks for the PR to get merged; unless it's a no-brainer, we like to have some community feedback on new features, before we merge them; this leads to higher-quality code, in the end; we learnt this the hard way :-)
• not all PRs get merged; sometimes we just have to hold out new features, to keep the packages lean; sometimes we don't include features that only apply to niche use cases;
• we're not perfect; if you think we're wrong, call us out on it; but in a kind way :-) we all make mistakes, best we learn from them and build better software together;

Thank you!

-- Justin Case The Backpack Robot

[pxpm]

Thanks for the pull request @gleb-svitelskiy really appreciate the time you spent here.

Unfortunately like I said in the issue comment we cannot merge this as this does not address your problem.

If you are using different tables you should configure them in the spatie config file like I said in https://github.com/Laravel-Backpack/CRUD/issues/5281#issuecomment-1683957080

Cheers

[pxpm]

Hey @gleb-svitelskiy I got the issue now. And I've checked Laravel docs to make sure it also accepts the model instead of the table name.

I will properly review this PR tomorrow or monday, but it's 99% guaranteed to get merged.

Sorry I need to spend some time here before merging that I can't afford today.

Thanks again, and sorry for the confusion 🙏

[pxpm]

Thanks again @gleb-svitelskiy and sorry for the confusion at first.

Merged and tagged 🙏

[welcome[bot]]

WHOOP-WHOOP! Congrats, your first PR on this repo has officialy been merged.

If you want to help out the community in other ways, you can:

• give your opinion on other Github Issues & PRs;
• chat with others in the Gitter Chatroom (usually for quick help: How do I do X);
• answer Backpack questions on Stackoverflow; you get points, people get help; you can subscribe to the backpack-for-laravel tag by adding a new filter; that will send you emails when new questions come up with our tag;

Again. Thank you for the PR. You are a wonderful person. Keep 'em coming :-) Cheers!

-- Justin Case The Backpack Robot

P.S. Help in the Backpack community is rewarded with free Backpack commercial licenses. It's the least we can do. If you feel you've helped the community with PRs, help & other stuff, please shoot Tabacitu an email and ask him if you qualify for free licenses. You scratch my back, I scratch your back. Thank you!