-
Notifications
You must be signed in to change notification settings - Fork 84
docs(clp-config): Add commented out default values to nullable mcp_server and presto in clp-config.yaml; Clarify configuration steps in the manuals.
#1635
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
base: main
Are you sure you want to change the base?
Conversation
…erver` and `presto` in `clp-config.yaml`; Clarify configuration steps in the manuals.
WalkthroughDocumentation and configuration template updates clarify MCP server and Presto setup instructions. The changes add host/port example values to the configuration template and revise user guides to provide explicit configuration steps rather than referential instructions. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes These are primarily documentation and configuration template updates with consistent, straightforward changes across files. Review focuses on verifying accuracy of examples and clarity of instructional messaging. Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: ASSERTIVE Plan: Pro 📒 Files selected for processing (3)
🧰 Additional context used🧠 Learnings (4)📓 Common learnings📚 Learning: 2025-08-25T16:27:50.549ZApplied to files:
📚 Learning: 2025-10-27T07:07:37.901ZApplied to files:
📚 Learning: 2025-10-02T15:48:58.961ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rishikeshdevsot may i get your approval for the modifications in this docs if they look good to you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davemarco may i get your approval for the modifications in this docs if they look good to you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think haiqi originally did not want to put the "default" port since there is no error when starting the package if the port is incorrect. Like he wanted to force the user to input their specific port
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm.. even if we ask users to provide a port, if we don't do any checks (i guess we really can't), there is no guarantee that the port is valid?
fwiw, i believe providing a default helps avoid collision with ports of other services in the CLP package / other well-known ports
Description
This PR updates configuration comments and user documentation for both the MCP server and Presto:
hostandportexample fields (commented out) to themcp_serverandprestosections inclp-config.yaml.guides-mcp-server, emphasizing uncommenting the block and replacing defaults when needed.localhost,8889) and clarifies that users may replace them if needed.These changes improve clarity for users configuring CLP components.
Checklist
breaking change.
Validation performed
task docs:serveand inspected the docs.Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.