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

[QUESTION] Should not found files not raise an error while executing collectstatic #776

Open
Schwankenson opened this issue Jan 5, 2023 · 6 comments
Labels

Comments

@Schwankenson
Copy link

When executing collectstatic django-pipeline does not raise an error if a file defined in PIPELINE config is not found. Is this on purpose? Do I miss a settings? I would like to get an error if file which should be compiled does not exist.

@peymanslh
Copy link
Member

Currently, Django-pipeline doesn't raise any error when files don't exist.

@Schwankenson
Copy link
Author

@peymanslh Thank you, I know. The question is: Why does it not raise an error. I find it hard to debug my file locations without it throwing an error. Should it not raise an error, at least in debug mode?

@peymanslh
Copy link
Member

The problem is pipeline doesn't work in debug mode, but it could be implemented as a feature with a flag in settings to throw an error when a file is not found. But as far as I know, it could be hard to implement!

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

No branches or pull requests

4 participants
@Schwankenson @peymanslh @Pyvonix and others