Thank you for your response, Ben. > IMO the jquery-migrate plugin shouldn't be included in production by > default, but it could be activated with a symbol constant.
I agree. How about -- instead of creating a new configuration symbol -- re-using 'tapestry.javascript-infrastructure-provider'? The default value is still 'prototype', by the way, but I intend to change that (see TAP5-2732). Setting it to 'query-migrate' would enable the jQuery Migration Plugin, for both production or development mode. I'll give it a try and push it to the TAP5-2734 branch when ready. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
