showInfobar setting is ignored (config reads "showInfo" instead)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with src/config.ts and inspect sanitizeConfig() and the legacy info migration; the issue identifies both incorrect keys and gives the suggested behavior. Run the reported sanitizeConfig() and fromQuery() cases for JSON, URL, legacy values, and unset defaults. Done when each case preserves the expected show or hide setting, including configs using the showInfo workaround.
Written by the indexing model from the issue text.
Description
Problem
"showInfobar": false in wall-config.json (or a ?load= config) has no effect; the info bar is always shown. The same happens with ?info=false in the URL and the "Show info bar" checkbox in the Customize dialog.
Cause
In src/config.ts, sanitizeConfig() reads the wrong key:
result.showInfobar = boolOr(config.showInfo, fallback.showInfobar)
config.showInfo is never set (the type, the URL parser and the generated config all use showInfobar), so it always falls back to the default (true).
A related typo in the legacy migration sets config.showinfo (lowercase), so the old info: "top"/"hide" values are ignored too.
Workaround for now: use "showInfo": false in the JSON config.
Suggested fix
if (isString(config.info))
- config.showinfo = config.info == "top"
+ config.showInfobar ??= config.info == "top"
...
- result.showInfobar = boolOr(config.showInfo, fallback.showInfobar)
+ result.showInfobar = boolOr(config.showInfobar ?? config.showInfo, fallback.showInfobar)
Keeping ?? config.showInfo means configs that already use the workaround keep working.
Tested by running sanitizeConfig() / fromQuery() from current main (b55d81c) with Node: before the fix, {showInfobar: false} and info=false both give true; after it, every case (JSON true/false, URL true/false, legacy "top"/"hide", unset → default) gives the expected value.
- Dominant language
- TypeScript
- Stars
- 95
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from defnull/fediwall
-
just saying hiOpen
Difficulty 1/5 Under an hour Newbie friendliness 1/100
-
bird.makeupOpen
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 39/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in defnull/fediwall
Similar issues
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is pickedOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
omdsh-dev/DSH-better-sidebar#1141 ·
Maintainers usually reply within 2 days
-
desktop linux photos
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Cleanup SetupPossibly taken @AlexanderKaran claimed this today. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
e18e/framework-tracker#769 ·
Maintainers usually reply within 1 day
-
bug v2
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/servers#5483 ·
Maintainers usually reply within 1 day