Skip to content
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

feat: combine custom command implementations from #47 and #53 #59

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

devin-ai-integration[bot]
Copy link
Contributor

This PR incorporates changes from #47 and #53, combining the custom command functionality from both PRs.

Original implementation in #47 by @matildepark
Additional changes from #53

Changes:

Link to Devin run: https://app.devin.ai/sessions/88d54527369a462c8710f0fb5732ae71

matildepark and others added 8 commits December 11, 2024 11:18
- Add 'custom' as valid runtime type
- Add required command and args fields for custom runtime
- Update validation in pr-check.js
- Add custom runtime support in ConfigManager
- Update type definitions and interfaces

Co-Authored-By: Michael Latman <[email protected]>
- Add proper fs module mocking for ESM environment
- Fix test state management between runs
- Add comprehensive error handling tests
- Update ConfigManager to use dynamic fs imports

Co-Authored-By: Michael Latman <[email protected]>
# Conflicts:
#	src/utils/config-manager.ts

Co-Authored-By: Michael Latman <[email protected]>
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR
  • Look at CI failures and help fix them

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Add "(aside)" to your comment to have me ignore it.

Copy link
Contributor

❌ No new packages found or validation failed.

Copy link
Contributor

✅ PR validation passed successfully!

Copy link
Owner

@michaellatman michaellatman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where are the tests?

@@ -23,6 +23,10 @@ export interface PackageHelper {
};
configureEnv?: (config: any) => Promise<void>;
runtime?: 'node' | 'python';
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Runtime should be custom right?

serverConfig.command = 'npx';
serverConfig.args = ['-y', pkg.name];
if (customCommand) {
serverConfig.command = customCommand.command;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Custom command should be handled in its own rumtime

} else if (pkg.runtime === 'python') {
serverConfig.command = 'uvx';
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we can basically just resolve the command and args based on runtime and custom command and then just set serverCOnfig.command and args based on that versus these if branches

Copy link
Contributor

❌ No new packages found or validation failed.

Copy link
Contributor

✅ PR validation passed successfully!

Copy link
Contributor

❌ No new packages found or validation failed.

Copy link
Contributor

✅ PR validation passed successfully!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants