fix(dependency_getter): avoid error on empty dependencies #752
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.
PR Checklist
docs
is updatedDescription of changes
We currently hard access
dependencies
key for both PEP 621 and Poetry projects to retrieve dependencies. Although not common, it could happen that projects usedeptry
, but do not have any production dependencies (for instance when bootstrapping a project from a minimal template, where you don't start with any dependency, but still want to includedeptry
in the CI workflow).This PR soft accesses dependencies for both PEP 621 and Poetry. As for Poetry, we rely on
dependencies
to determine if a project uses Poetry, the logic is also updated to assume that a project uses by only checking[tool.poetry]
instead of[tool.poetry.dependencies]
. This should not be problematic, as[tool.poetry]
is specific to Poetry, and Poetry only.