You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 5.1, Django includes a built-in querystring templatetag. However, when loading the django_tables2 templatetag library, the built-in tag is shadowed. Since these templatetags are incompatible, it leads to some confusion, which will only grow as usage of the built-in querystring becomes more widespread.
So far, I have considered the following alternatives:
Moving the querystring templatetag to a separate library (for example django_tables2_utils).
Renaming the querystring templatetag to something else, like query_replace or querystring_replace
A combination of (1) and (2)
Unfortunately, none of these alternatives is backward-compatible if the user has copied/modified the default table templates for their project.
The text was updated successfully, but these errors were encountered:
Since version 5.1, Django includes a built-in
querystring
templatetag. However, when loading thedjango_tables2
templatetag library, the built-in tag is shadowed. Since these templatetags are incompatible, it leads to some confusion, which will only grow as usage of the built-inquerystring
becomes more widespread.So far, I have considered the following alternatives:
querystring
templatetag to a separate library (for exampledjango_tables2_utils
).querystring
templatetag to something else, likequery_replace
orquerystring_replace
Unfortunately, none of these alternatives is backward-compatible if the user has copied/modified the default table templates for their project.
The text was updated successfully, but these errors were encountered: