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

Default modules #5

Closed
andrewdavey opened this issue Jul 25, 2011 · 4 comments
Closed

Default modules #5

andrewdavey opened this issue Jul 25, 2011 · 4 comments

Comments

@andrewdavey
Copy link
Owner

The current default is for each sub-directory of "scripts", "styles", "htmlTemplates" to be a module.
This is confusing for new users, especially when it comes to stylesheets.

An alternative default is to treat the entire web application as a single module. So the default path is "~/" for each asset type.

This would be simpler for small web applications. More complex apps can always edit the web.config for more advanced module definitions.

@sfmskywalker
Copy link

Could be handy, lthough personally I love using the modules setup, even though I'm a new user :)

@andrewdavey
Copy link
Owner Author

v0.5.3 treats the entire application root directory as a single module.

This can the be overridden in web.config to restore the previous, more complex behaviour, using:

<cassette>
  <scripts>
    <add path="scripts/*"/>
  </scripts>
  ...
</cassette>

@sfmskywalker
Copy link

Great :)

FYI: I just installed Cassette via NuGet a few minutes ago, and I'm receiving version 0.5.2.

@andrewdavey
Copy link
Owner Author

Cassette 0.6 now treats the entire application as a single module by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants