Skip to content

chore: drop debug logs and the unused weather build arg; 400 on a bad settings search - #297

Merged
jherforth merged 1 commit into
jherforth:mainfrom
mrramam:chore/client-cleanup
Oct 21, 2026
Merged

jherforth merged 1 commit into
jherforth:mainfrom
mrramam:chore/client-cleanup

Conversation

@mrramam

@mrramam mrramam commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

The remaining items from mrramam#74.

  • Debug logs removed.
    • AdminPanel's profile picture upload logged the file's name, size and type, and the upload response.
    • ChoreWidget logged the username and picture path on every failed avatar load, which repeats on an always-on display.
    • Both are gone, along with the now-unused uploadingPicture string. Errors still log.
  • Unused build arg removed. client/Dockerfile still declared VITE_OPENWEATHER_API_KEY. Nothing reads it since weather moved server-side, and configuration.md already called it unused. It's removed from the Dockerfile, CONTRIBUTING.md, getting-started.md, configuration.md and frontend.md, so a client-side key isn't invited back.
  • A bad settings search is a 400. POST /api/settings/search wraps a non-array body in an array and calls replaceAll on each key, so a number, an object or no body threw and answered 500. It now answers 400 unless every key is a string. There's a new case in apiEndpoints.test.js, which fails without the check.

The server's === SEARCHING SETTINGS === line stays, because secretsInLogs.test.js uses it to show the route's logging was captured.

Server and client suites, check:i18n and the client build pass.

… settings search

- AdminPanel's profile picture upload logged the file's name, size and type
  and the upload response; ChoreWidget logged the username and picture path
  on every failed avatar load, which repeats on an always-on display. Both
  removed, with the now unused uploadingPicture string. Errors still log.
- client/Dockerfile still declared VITE_OPENWEATHER_API_KEY as a build arg
  and env var. Nothing reads it since weather moved server-side, and the
  docs called it unused. Removed from the Dockerfile and from the setup
  docs, so a client-side key isn't invited back.
- POST /api/settings/search wraps a non-array body in an array and calls
  replaceAll on each key, so a number, an object or no body threw and
  answered 500. It now answers 400 unless every key is a string.

The server's "=== SEARCHING SETTINGS ===" line stays: secretsInLogs.test.js
uses it to show the route's logging was captured.
@jherforth jherforth added the enhancement New feature or request label Oct 21, 2026
@jherforth jherforth added this to the 1.10 milestone Oct 21, 2026
@jherforth
jherforth merged commit 196182b into jherforth:main Oct 21, 2026
3 checks passed
@github-project-automation github-project-automation Bot moved this from Backlog to Done in HomeGlow Kanban Oct 21, 2026
@jherforth jherforth added refactor Code cleanup task and removed enhancement New feature or request labels Oct 21, 2026
@mrramam
mrramam deleted the chore/client-cleanup branch October 21, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor Code cleanup task

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants