-
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
convert
fails conda-smithy linter
#280
Comments
As for the trailing whitespace, I don't think this is the fault of the CRM project. In other words, CRM did nothing wrong, this is a tabs-vs-spaces-esk styling debate. We are not beholden to the preferences of We could add a flag to control the trailing whitespace. Honestly if this is being run in an automated environment, I would just run a |
thanks, opened conda-forge/conda-smithy#2201 |
I'm sorry if I'm missing something but to the best of my knowledge, the debate is about having trailing newline and not having a trailing newline. However, conda-recipe-manager generates two trailing newlines (i.e. |
Two newlines? I only see one blank line at the end of the diff provided. One blank line is also all I have ever seen come out of this tool and what our CRM unit tests have. Maybe the diff provided is incorrect? Am I missing something? |
@mgorny is correct: conda-forge/array-api-extra-feedstock@248c736 |
Okay, I'm getting tripped up on the visualization here and had to sanity checked myself with Anyways, I'm just going to change it. I could have sworn this was the preferred style in AnacondaRecipes and/or Bioconda but I'm looking again and I don't see a huge preference. It probably just isn't as strictly enforced. |
Dealt with in: #283 will be in the next release |
thanks! |
What happened?
The following diff was needed to pass the conda-smithy linter after using convert:
To Reproduce
Steps to reproduce the behavior:
crm convert
on https://github.com/conda-forge/array-api-extra-feedstock/blob/e9fe7f3a6a0b3cbfbc33aaa167e0b020fac7e916/recipe/meta.yamlAdditional Details (please complete the following information):
version 0.4.0
The text was updated successfully, but these errors were encountered: