There aren't any mandatory rules but standards to make code maintainable,
following standards you shouldn't do it but depends upon how much work you
need to do for each user type and how much closely they are linked to each
other. if there is no or minimal link and a lot of switching will be needed
Hi,
That is for you to decide - that's a project specific decision.
However I wouldn't do that - I would filter the html templates and only
display the items that should be displayed to each user type. Then I would
add checks to the views so that the user is the correct type to display the
view.
Yes, i have checked this article many times. It tells you how to implement
user model to handle multiple user types not on how the apps should be laid
out in that case.
My question was if you have 5 types of users in your website and each user
has different interfaces and tasks to perform. Sho
I think you don't need several apps for each user type. You have different
ways to approach it, one could be used with permisology policy for each
model and each user type in the Django app, other one could be managing the
policies by yourself.
I suggest to search in Google a entry in the blog
sim
Hi,
a new Django app should be based on a new business feature/aspect, not user
type.
If different behavior needed for different type of user, you can check the
permission or group of the user:
https://docs.djangoproject.com/en/2.2/topics/auth/default/
On Mon, Oct 14, 2019 at 6:33 AM test user wr
Hi,
I have got multiple user types(around 4 to 5) in my Django project. Should
i make separate Django app for each user type? Each user type will have
different interface after they log into the website.
--
You received this message because you are subscribed to the Google Groups
"Django user
6 matches
Mail list logo