Conversation
Reviewer's Guide by SourceryThis pull request introduces support for managing project tools using asdf. It adds a Sequence diagram for asdf tool installation processsequenceDiagram
participant D as Developer
participant M as Makefile
participant A as asdf
participant TV as .tool-versions
D->>M: make asdfi
M->>TV: Read tool list
M->>A: Add plugins for each tool
A-->>M: Plugins added
M->>A: asdf install
A->>TV: Read tool versions
A-->>M: Tools installed
M-->>D: Installation complete
File-Level Changes
Assessment against linked issues
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Hey @JaeAeich - I've reviewed your changes - here's some feedback:
Overall Comments:
- The
.tool-versionsfile appears to be empty. Please add the required tool version specifications to make this change functional.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
@sourcery-ai review |
|
@sourcery-ai summary |
There was a problem hiding this comment.
Hey @JaeAeich - I've reviewed your changes - here's some feedback:
Overall Comments:
- The .tool-versions file appears to be empty in the diff. Please include its intended contents so we can review the tool specifications.
- Consider adding documentation about the expected format and usage of the '# INSTALL:' commands in .tool-versions, since this is a custom implementation.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
@uniqueg I do agree that maybe What do you think? is that the way to go, or if its not hacky enough we can try to over engineer |
I would
That way, Now, for installing tools that are not covered by |
|
@sourcery-ai review |
|
@sourcery-ai summary |
There was a problem hiding this comment.
Hey @JaeAeich - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
uniqueg
left a comment
There was a problem hiding this comment.
Please prompt the user for the desired Poetry version, just like you do for the Python version.
.tool-versions.tool-versions and prompt for poetry_version

Description
.tool-versions#27Also prompt for poetry version, ref.
Checklist
project, including, in particular, with regard to any style guidelines
specification; in particular, it clearly indicates
that a change is a breaking change
using the PR title as the commit message
changed behavior
or updated existing ones (only for Python, TypeScript, etc.)
docstrings) for all packages/modules/functions/classes/
methods or updated existing ones
works
Comments
Summary by Sourcery
Add support for managing the development environment with asdf.
New Features:
asdfito install tools based on the.tool-versionsfile.Enhancements:
.tool-versionsfile to specify tool versions.Documentation: