Closed szepeviktor closed 1 year ago
Although naming 3rd-party packages $BRAND-$PURPOSE is highly popular!
naming is fine. i would recommend to just stick with the current schema 😜
All right, all right.
I am open to naming changes but I don't really give the package a recognizable on the docs. It is just described by it behavior. The only real usage that could be changed is the composer name - and I won't change that as there is already quite a sizeable install base using that name.
It would be a change without giving any benefits.
I just wanted to plant this thought in your head.
Laravel PostgreSQL Enhanced suggests it has something to do with the company behind the Laravel framework.
"Enhanced PostgreSQL for Laravel" or "PostgreSQL Enhancements for Laravel"
What do you think?