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
The limitations we are facing are best summed up as:
the jQuery UI objects look for jQuery in the global context. Because of require sandboxing, this isn't available by default. We could solve this by using the pointcuts syntax, but that yields issue 2 below
The current syntax doesn't allow for an easy way to package this up. You'd end up with a huge manifest, when really all you need is smarter regex rules
The result of this is a proposal for a new syntax that would deprecate require.manifest in favor of simpler additive rules
total time to run matches would be n regex/string checks
if you find a match, do you abort early, or do you continue down the stack? On one hand, continuing down the stack is pretty powerful as far as matching rules go. On the other, that's a ton of overhead potentially.
weight is listed as optional. Should faux-constants be created under require.CONSTANTS, or should we leave it up to the developer to weight their rules accordingly. By default, later rules would receive a higher index if not overridden.
I pieced together a sample bit of code for what including jquery might look like. My biggest concern is the addRule still feels pretty unwieldy for the more robust examples. It's certainly better than having dozens of repeated code lines though for each jQuery UI module.
Through conversation with @PeterFrueh, jquery's UI modules are difficult to load. In theory, we should be able to maintain the standard syntax:
The limitations we are facing are best summed up as:
jQuery
in the global context. Because of require sandboxing, this isn't available by default. We could solve this by using the pointcuts syntax, but that yields issue 2 belowThe result of this is a proposal for a new syntax that would deprecate require.manifest in favor of simpler additive rules
The text was updated successfully, but these errors were encountered: