Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve optimization in on and optimize #14

Open
Swaagie opened this issue Aug 22, 2014 · 0 comments
Open

Resolve optimization in on and optimize #14

Swaagie opened this issue Aug 22, 2014 · 0 comments

Comments

@Swaagie
Copy link
Member

Swaagie commented Aug 22, 2014

Currently the paths of dependencies, css, js and the view are resolved twice. This allows for more flexibility in the use of .on. Per example, providing relative paths, then resolving those via on to make adjustments later on in optimize is a viable strategy. Contour adopts this strategy by replacing parts of the paths.

Double calls however limit performance, so perhaps we could use a flag to acknowledge the use of on, or use the presence of prototype.directory as flag. This should prevent iterating the assets folders twice.

@Swaagie Swaagie changed the title Resolve optimization in on and optimize Resolve optimization in on and optimize Aug 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant