php artisan backpack:build on our demo highlights a bunch of minor problems #159
Description
Bug report
What I did:
php artisan backpack:build
What I expected to happen:
Everything work. Solve world hunger. Bring world peace. Help humanity ascend to a higher plane of understanding.
What happened:
NONE of the above!!! 😱 I don't think it's worth addressing world hunger, world peace in v5 though... those might take too much time to develop (6+ months probably) so maybe we focus on the minor things that didn't work? We can probably fix those in v5.
Here's a few things I noticed:
- 🟡 didn't ask me what kind of validation I want... so it just created Requests for all models; bleah; @promatik
- 🟡 highlighted how confusing up our example entities are, the ones that relate to Monster - sorry @pxpm but PostalBoxes, PostalBoxer, Recommends, Sentiments, Stars, Universes, Wishes, Balls, Bills, Graffiti... those don't make sense... let's spend 30min on it together, and see how we can rename them, so that when people look at them, they just "get it";
- 🔵 a new
admin/petsidebar item has been added, even if it existed; I wonder why... and if there actually is anything to fix here or it's just the way it is; (the route didn't get created, which is ok, it existed in the pet-shop prefix); same thing happens foradmin/skill,admin/passport,admin/owner,admin/invoice,admin/comment,admin/badge - ❓add Wish doesn't work... error 500... why?
- ❓add Story doesn't work... error 500... why?
- ❓add PostalBoxer doesn't work... error 500... why?
- ❓add PostalBox doesn't work... error 500... why?
- ❓add Address doesn't work... error 500... why?
- 🔵 a new
admin/productsidebar item has been added, even if it already existed as a subitem above; perhaps the check we do is a little too strict? I don't know how it works, but off the top of my head, if there's an item pointing toadmin/productin the sidebar... we should no longer add it; so... route-based;