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

[Feature Request] exclusion of file from processing #170

Closed
krrishd opened this issue Dec 3, 2013 · 3 comments
Closed

[Feature Request] exclusion of file from processing #170

krrishd opened this issue Dec 3, 2013 · 3 comments

Comments

@krrishd
Copy link

krrishd commented Dec 3, 2013

Hi guys,

I just was wondering if a certain feature would be feasible: the ability to exclude a certain file (LESS, Markdown, etc) from being compiled. For example, I want to create a README.md, but it gets compiled to HTML or gets deleted by a new compilation.

@kennethormandy
Copy link
Collaborator

I’m not sure how this could work for other preprocessors, but for Markdown, you should be able to rename the file README.markdown or README.txt or one of the other extensions and it won’t be compiled. Harp only looks for .md files.

@silentrob
Copy link
Collaborator

@krrishd The idea is to have convention over configuration. There are a few ways to solve this.
As @kennethormandy mentioned using a un-preprocessed file will achieve that or you can hide the file from the preprocessor by prefixing it with underscore _README.md.

We also have two types of app styles, root and framework. If you opt for a framework style app you can have all compiled asstes in a public folder and the README.md in the root folder and it will not get processed.

Lastly, Harp will not compile assts in their final form. So naming a file css or html is also ignored.

Hope that helps.
Rob

@krrishd
Copy link
Author

krrishd commented Dec 3, 2013

Thanks guys, I just wasn't sure if .markdown would be compiled.

On Tuesday, December 3, 2013, Rob Ellis wrote:

@krrishd https://github.com/krrishd The idea is to have convention over
configuration. There are a few ways to solve this.
As @kennethormandy https://github.com/kennethormandy mentioned using a
un-preprocessed file will achieve that or you can hide the file from the
preprocessor by prefixing it with underscore _README.md.

We also have two types of app styles, root and framework. If you opt for a
framework style app you can have all compiled asstes in a public folder and
the README.md in the root folder and it will not get processed.

Lastly, Harp will not compile assts in their final form. So naming a file
css or html is also ignored.

Hope that helps.
Rob


Reply to this email directly or view it on GitHubhttps://github.com//issues/170#issuecomment-29733575
.

---------

Krish Dholakiya

Founder/CEO - Classify Studios

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

3 participants