FWIW The template system always seemed like an added bonus to the project. Which is fine because, personally, I’d rather more effort go into the guts than the lipstick anyway.
It’s easy enough to build custom filters, or even exploit some of the quirks of the system… so much so that asking the core team to address this over just building or forking a third-party package is superfluous. All that said, it loos like you’re trying to build form fields based on a predetermined, um, range of results. It looks to me this can be addressed by having one more nested loop. So you have `for i in group` then `for j in i.game` - you could add something like `for k in j.squad_entry_members`. This would skip the need for a range, fall within the system specs, and gets you a free counter without having to know the specific size. Benny > On Oct 9, 2021, at 5:45 AM, 'Adam Johnson' via Django developers > (Contributions to Django itself) <django-developers@googlegroups.com> wrote: > > > Please don't use shouty capitals or angry slang like "Bruh no" on this > mailing list. This mailing list is for calm professional discussion. > >> On Sat, 9 Oct 2021 at 11:35, Dhruva Shaw <dhruvas...@gmail.com> wrote: >> SINCE THE NO OF SELECT BOXES THAT I HAVE GENERATE COMES DIRECTLY FROM THE >> DATABSE, THUS RANGE FUNCTION IS NEEDED! >> >>> On Saturday, October 9, 2021 at 2:40:29 PM UTC+5:30 f.apo...@gmail.com >>> wrote: >>>> On Friday, October 8, 2021 at 6:14:19 PM UTC+2 dhruv...@gmail.com wrote: >>>> Ik range function can be added but I also mentioned that there are some >>>> cases range function can't be direct generated from the view like this >>>> https://github.com/Tanzanite-lpu/tgl-2.0.0/blob/ddce5ef87a4b5248b8cb8cd5fa3df4adb3f00b31/main/templates/groups.html#L36 >>> >>> Why was "|range" added there? You are not using {{ j }} there at all but {{ >>> forloop.counter }}. There doesn't seem to be any reason to use "|range" >>> there. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/3e733a40-b9a0-4bc7-ba87-943bc5aee635n%40googlegroups.com. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMyDDM3MsvujxsH_QtHyO4Pqo6Vgtd1bG%2BTHB4_GYx%2BpQ2xGRA%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/32AF05A5-DFD8-47A0-A671-959FAB725980%40twosensedesign.com.
