I wonder if it's feasible to monkeypatch debugging wrappers around jQuery core methods. You don't even need it to throw errors -- a simple console.log warning would suffice.
-- dz On Tue, May 19, 2009 at 8:38 AM, Julian Aubourg <aubourg.jul...@gmail.com> wrote: > jquery.debug.js / jquery.release.js ? ;) > I really like this idea. When I first started using jQuery, I sometimes had > some issues determining what it was I was doing wrong when jQuery complained > deep in its internal functions. > > 2009/5/19 Matt Kruse <m...@thekrusefamily.com> >> >> On May 19, 5:32 am, DBJDBJ <dbj...@gmail.com> wrote: >> > This is an discussion on library develeopment philosophy. >> > There are only two sides to this coin: fast and dangerous and safe and >> > slow. >> >> I think this is another use for a jQuery "development" build. One that >> would generate warnings of empty selector results, invalid arguments, >> etc. It could also detect possible conflicts like this that would >> cause jQuery to misbehave and alert the developer. >> >> Once development is done, you swap in the "production" version of >> jQuery and avoid the penalty his that comes with all the debug stuff. >> >> Matt Kruse >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
