-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
hassfest: Unable to parse package version when requirement contains git #92
Comments
This appears to still be an issue, however based o the updated docs
hassfest errors out with Error: R] [REQUIREMENTS] Requirement ...blah... contains a space It seems to be failing due to the SPACE@SPACE |
Components that declare a requirement as stated above do work as expected. It seems that just the hassfest test is not aware of this format. |
Hi @mpw96 perhaps you can help/clarify. This still doesn't seem to be working.
This is still rejected by hassfest@master with the error:
Which is still how the documentation at https://developers.home-assistant.io/docs/creating_integration_manifest/#custom-requirements-during-development--testing specifies we reference public github repo's for requirements. "requirements": [" @ git+https://github.com//.git@"] Is the documentation wrong or is hassfest validation wrong? |
Hi I just wanted hassfest in my component not to cmplain anymore, that's why I proposed the change - I hope I didn't make things worse for anybody! Here is what works for me:
So your code should be like this I think:
Does it work? |
So what @mill1000 needs should actually work now. |
I ran a test here and it seems to be working: mill1000/midea-ac-py#268 |
thanks, yes using this formatting now works, I'll put a PR in to update documentation as I think that will still be throwing people off. Thanks all :) |
…nal git library As in issue home-assistant#92 (home-assistant/actions#92) this update to documentation corrects this in line with hassfest validation.
As in issue #92 (home-assistant/actions#92) this update to documentation corrects this in line with hassfest validation.
I'm attempting to run hassfest against a custom component that currently uses a git repository as a requirement. I'm using the format specified by the docs here.
e.g.
hassfest is failing with the following error:
The text was updated successfully, but these errors were encountered: