Re: Custom Groups model and interoperability

I think a big part of the challenge I'm experiencing with the user of my reusable app who has submitted the controversial PR is that the "semi-official position" is undocumented in Django. I see a 3 yr old Track ticket requesting implementation of a

Re: Custom Groups model and interoperability

Thanks very much for the response Aymeric. Seems like a bit of a gray area that could use some form of recommendation - like in a "Best Practices" section of the documentation? In any case, thanks again. Scot On Tuesday, October 5, 2021 at 1:13:47 PM UTC-7 Aymeric Augustin wrote: > Hello, > >

Re: Custom Groups model and interoperability

Hello, The semi-official position is "create a separate model with a FK to the auth.Group". I know that's less than helpful. At least you know that there's nothing better built-in. -- Aymeric. PS: `{% block content %}` doesn't provide a meaningful level of interoperability. The semi-official

Re: Custom Groups model and interoperability

No official (or semi-official) position on this? Is "The right way to create custom Groups" simply undefined in Django? Thanks. On Sunday, October 3, 2021 at 10:27:36 PM UTC-7 Scot Hacker wrote: > I asked this question on django-users and got no response. Thought I might > have better luck

Custom Groups model and interoperability

I asked this question on django-users and got no response. Thought I might have better luck getting an "official" opinion on this here. You can call blocks in your templates anything you like, but if you intend to share your software with the world, you'd better use `{% block content %}` if you