On 7 Jun 2006, at 04:11, Adrian Holovaty wrote:
> * THROW ERROR ON FORM DISPLAY: If the APPEND_SLASH setting is set to > True and the CommonMiddleware is activated, Django could check the > output of every page for a <form> whose method is POST and has an > "action" whose URL doesn't end in a slash. Then it could somehow alter > the page to display an error on it. This solution is horrific, but I'm > mentioning it here for diversity. That's certainly horrific as a regular built-in feature of the framework that runs all the time, but behaviour like this might be well suited to a separate "Django lint" tool. Since Django as all about best practises, it might be interesting to put together a lint tool (maybe using the unit testing hooks that we've been talking about for so long) some time in the future. It's certainly a nasty solution here, but we shouldn't rule inspecting generated pages for errors out completely - just as long as anything like that is hived off in to a specialist tool. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
