-
Notifications
You must be signed in to change notification settings - Fork 9
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
Validate fields pointing to paths #89
Comments
I am on the fence for this one... Adding a feature like this means that we validate |
We could, potentially, achieve something with warnings and having a CLI flag to transform warnings in errors, but the
|
I agree, that this feels strange from the aspect of validating two different things out of the developer perspective. Out of the users perspective on the other hand it feels strange, that these things are separated. Sorry, I do not understand why thread safety is a concern here. Is the validation process multi-threaded? |
@marscher, |
That's a valid point. Although I think it is unlikely that developers will fiddle around with the environment during execution the validation. But it can happen of course. Then it'd be super hard to detect or work around this circumstance. If this causes too much of an headache, I'd be fine with closing my request. |
Fields allowing for files are:
It would be very nice of
validate-pyproject
, if it could raise when one of these files are not accessible. It just happened to me during transitioning from RST to Markdown for the readme, that I forgot to adopt this. And I used validate-pyproject as a pre-commit hook.I'd also be happy to submit a PR for this.
The text was updated successfully, but these errors were encountered: