vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 23:57:11 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[PR #141] [MERGED] fix: remove debug console.log statements from settings-prompt #187

New Issue
Closed
opened 2026-06-06 22:09:36 -04:00 by yindo · 0 comments
yindo commented 2026-06-06 22:09:36 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/141
Author: @mason5052
Created: 2/23/2026
Status: ✅ Merged
Merged: 2/23/2026
Merged by: @asdek

Base: feature/project_improvements ← Head: fix/remove-debug-console-logs

📝 Commits (1)

  • eda4764 fix: remove debug console.log statements from settings-prompt

📊 Changes

1 file changed (+0 additions, -7 deletions)

View changed files

📝 frontend/src/pages/settings/settings-prompt.tsx (+0 -7)

📄 Description

Description of the Change

Problem

settings-prompt.tsx contains 7 leftover console.log calls on success paths that were introduced during development but should not be present in production code:

  • 'Prompt reset to default successfully'
  • 'Template is identical to default, skipping save'
  • 'System prompt updated successfully'
  • 'System prompt created successfully'
  • 'Human template is identical to default, skipping save'
  • 'Human prompt updated successfully'
  • 'Human prompt created successfully'

Solution

Remove all 7 debug console.log statements. Error paths using console.error are intentionally kept.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

Areas Affected

  • Core Services (Frontend UI/Backend API)

Testing and Verification

Test Steps

  1. Open browser DevTools console
  2. Perform prompt reset, create, and update actions in Settings
  3. Confirm no debug messages appear in console (only errors if they occur)

Security Considerations

No security implications.

Checklist

Code Quality

  • My code follows the project's coding standards
  • All new and existing tests pass
  • I have run npm run prettier and npm run lint (for TypeScript code)

Security

  • I have considered security implications
  • Changes maintain or improve the security model

Compatibility

  • Changes are backward compatible

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/vxcontrol/pentagi/pull/141 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 2/23/2026 **Status:** ✅ Merged **Merged:** 2/23/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/project_improvements` ← **Head:** `fix/remove-debug-console-logs` --- ### 📝 Commits (1) - [`eda4764`](https://github.com/vxcontrol/pentagi/commit/eda476419da49a60faa4d75aab2ba2224dc9ed1e) fix: remove debug console.log statements from settings-prompt ### 📊 Changes **1 file changed** (+0 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `frontend/src/pages/settings/settings-prompt.tsx` (+0 -7) </details> ### 📄 Description ## Description of the Change ### Problem `settings-prompt.tsx` contains 7 leftover `console.log` calls on success paths that were introduced during development but should not be present in production code: - `'Prompt reset to default successfully'` - `'Template is identical to default, skipping save'` - `'System prompt updated successfully'` - `'System prompt created successfully'` - `'Human template is identical to default, skipping save'` - `'Human prompt updated successfully'` - `'Human prompt created successfully'` ### Solution Remove all 7 debug `console.log` statements. Error paths using `console.error` are intentionally kept. ### Type of Change - [x] Bug fix (non-breaking change which fixes an issue) ### Areas Affected - [x] Core Services (Frontend UI/Backend API) ### Testing and Verification #### Test Steps 1. Open browser DevTools console 2. Perform prompt reset, create, and update actions in Settings 3. Confirm no debug messages appear in console (only errors if they occur) ### Security Considerations No security implications. ### Checklist #### Code Quality - [x] My code follows the project's coding standards - [x] All new and existing tests pass - [x] I have run `npm run prettier` and `npm run lint` (for TypeScript code) #### Security - [x] I have considered security implications - [x] Changes maintain or improve the security model #### Compatibility - [x] Changes are backward compatible --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-06 22:09:36 -04:00
yindo closed this issue 2026-06-06 22:09:36 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#187
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?