Carlton Gibson @carlton@chaos.social
Public

Django's query string tag (from v5.1) is a good example of a maintenance slow-bleed.

It **seems** simple but, over the space of users, has so many possible (i.e. actual) applications that there's a long stream of requests and revisions needed.

When folks are like "Why can't we **just** add feature…?" it's because they simply don't see what **just** adding that feature entails.

forum.djangoproject.com/t/enha

Enhancement Proposal for querystring template tag: Support for dynamic context-based keys

Problem Statement Currently, the {% querystring %} template tag treats the keys in kwargs as static strings. While this works for simple use cases, it severely limits the reusability of templates in component-based architectures. When using {% include %} to render a reusable component (like a generic filter, a sortable table header, or a pagination widget), the parameter name (the key) often needs to be dynamic, just like the value. The Use Case Imagine a reusable include for a sortable colu...

forum.djangoproject.com · Django Forum

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://publicidentity.net/users/jezdez/statuses/116124549325193133 on your instance and quote it. (Note that quoting is not supported in Mastodon.)