#18394: Add warning for invalid JavaScriptCatalog 'packages'
--------------------------------------+------------------------------------
Reporter: James Bennett | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Internationalization | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham):
Instead of a `RuntimeWarning` as proposed in the PR, would it make more
sense to raise a deprecation warning and eventually error out (or even
error out now)? I usually favor raising an error straight away, rather
than delaying that notice with a deprecation path, if it reveals a mistake
a developer made (a past case was `QuerySet.select_related()` validating
the values it receives) but I'll defer a decision here since I'm not a
`JavaScriptCatalog` user.
--
Ticket URL: <https://code.djangoproject.com/ticket/18394#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.43a81b35ed94f3a30e7636461920c175%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
