-
Notifications
You must be signed in to change notification settings - Fork 55
LCORE-247: Better service name in config file #308
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| name: foo bar baz | ||
| name: Lightspeed Core Service (LCS) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Verification agent 🧩 Analysis chainName updated – search for stale references Renaming to “Lightspeed Core Service (LCS)” looks correct. 🏁 Script executed: #!/bin/bash
# Find any leftover occurrences of the old placeholder
rg -n --ignore-case 'foo bar baz'Length of output: 422 Update all stale “foo bar baz” references The placeholder name “foo bar baz” still appears in several files. Please replace these with “Lightspeed Core Service (LCS)” to ensure consistency across configs, docs, and tests:
🤖 Prompt for AI Agents |
||
| service: | ||
| host: localhost | ||
| port: 8080 | ||
|
|
||
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.
Inconsistent example still shows old service name
The top-level
info.title/descriptionwere fixed, but the example response inside/v1/configstill returns"name": "foo bar baz"(≈ line 235).This inconsistency will confuse clients generated from the spec.
Additional change required outside this hunk:
📝 Committable suggestion
🤖 Prompt for AI Agents