Normalizing path of requirement files #406
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A requirements file could contain a relative link to another requirements file. If the link contains a
..
it can not be handled by the GitLab api.A short example:
The file requirements/production.txt contains the following:
Pyup adds the file path
requirements/../subproject/other_requirements.txt
to the list of requirement files. The request to fetch this file from the GitLab api is then responded with an HTTP 400 Error.By normalizing the file path before it is added this error is resolved. In our example the file path then would be
subproject/other_requirements.txt
.