11–20 of 86 posts
Rails and Phoenix also offer similar features (called scaffolds), but they are optional. I’m sure other frameworks have similar options.
Meanwhile, Django (like Python) sometimes has unconventional names and approaches to doing common things, so that makes the pair unpleasant and awkward for those of us with experience with several other tools and frameworks.
Mostly because it is dangerous (or was). For example, an integer that can only be 1, 2, or 3. In the admin (way back in the day, at least), someone could go into the admin and set it to 4. Which would then break everything in subtle ways. Also, most applications have constraints like "X can only be 2 if and only if Y is equal to Z" ... there was no way to specify that constraint to the admin interface, so someone cou…
It’s mostly just a UI for CRUD. And most systems are more complex, requiring UIs that operate on business logic. Rails and Phoenix also offer similar features (called scaffolds), but they are optional. I’m sure other frameworks have similar options. Meanwhile, Django (like Python) sometimes has unconventional names and approaches to doing common things, so that makes the pair unpleasant and awkward for those of us wi…
Citation needed. We also have got a _lot_ of mileage out of it over the years.
Mostly because it is dangerous (or was). For example, an integer that can only be 1, 2, or 3. In the admin (way back in the day, at least), someone could go into the admin and set it to 4. Which would then break everything in subtle ways. Also, most applications have constraints like "X can only be 2 if and only if Y is equal to Z" ... there was no way to specify that constraint to the admin interface, so someone cou…
Mostly because it is dangerous (or was). For example, an integer that can only be 1, 2, or 3. In the admin (way back in the day, at least), someone could go into the admin and set it to 4. Which would then break everything in subtle ways. Also, most applications have constraints like "X can only be 2 if and only if Y is equal to Z" ... there was no way to specify that constraint to the admin interface, so someone cou…
I don't know Django but doesn't model validation apply to the admin screens?
This is a convention though - one could just as easily do it the other way and embed all the business rules in the models.
https://symfony.com/bundles/EasyAdminBundle/current/index.ht...
Admin for Laravel (PHP) https://nova.laravel.com/
Java Spring Boot https://docs.spring-boot-admin.com/current/getting-started.h...
I think many other Frameworks have this, did you search for it?
Mostly because it is dangerous (or was). For example, an integer that can only be 1, 2, or 3. In the admin (way back in the day, at least), someone could go into the admin and set it to 4. Which would then break everything in subtle ways. Also, most applications have constraints like "X can only be 2 if and only if Y is equal to Z" ... there was no way to specify that constraint to the admin interface, so someone cou…
I don't know Django but doesn't model validation apply to the admin screens?
Admin for Symfony Framework ( PHP ) https://symfony.com/bundles/EasyAdminBundle/current/index.ht... Admin for Laravel (PHP) https://nova.laravel.com/ Java Spring Boot https://docs.spring-boot-admin.com/current/getting-started.h... I think many other Frameworks have this, did you search for it?
Mostly because it is dangerous (or was). For example, an integer that can only be 1, 2, or 3. In the admin (way back in the day, at least), someone could go into the admin and set it to 4. Which would then break everything in subtle ways. Also, most applications have constraints like "X can only be 2 if and only if Y is equal to Z" ... there was no way to specify that constraint to the admin interface, so someone cou…