Skip to content

[bug] useLightning remove double space#1005

Merged
accius merged 1 commit into
accius:Stagingfrom
MichaelWheeley:useLightning_double_space
May 21, 2026
Merged

[bug] useLightning remove double space#1005
accius merged 1 commit into
accius:Stagingfrom
MichaelWheeley:useLightning_double_space

Conversation

@MichaelWheeley
Copy link
Copy Markdown
Contributor

What does this PR do?

per #993 (review)
remove double space

Type of change

  • Bug fix
  • New feature
  • Performance improvement
  • Refactor / code cleanup
  • Documentation
  • Translation
  • Map layer plugin

Checklist

  • App loads without console errors
  • Tested in Dark, Light, and Retro themes
  • Responsive at different screen sizes (desktop + mobile)
  • If touching server.js: caches have TTLs and size caps (we serve 2,000+ concurrent users)
  • If adding an API route: includes caching and error handling
  • If adding a panel: wired into Modern, Classic, and Dockable layouts
  • No hardcoded colors — uses CSS variables (var(--accent-cyan), etc.)
  • No .bak, .old, console.log debug lines, or test scripts included

Copy link
Copy Markdown
Owner

@accius accius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed this is a correct one-character cleanup. distStr is built with a leading space already ( (${PROXIMITY_RADIUS_KM} km)), so the prior nearbyStrikes')} ${distStr} rendered a double space. Dropping the literal space matches the sibling usage at lines 848-851, where distStr is concatenated directly without an extra space.

Low risk, no functional change beyond the visible header text, CI is green. Looks good to me.

— K0CJH

@accius accius merged commit b5c1414 into accius:Staging May 21, 2026
5 checks passed
@MichaelWheeley MichaelWheeley deleted the useLightning_double_space branch May 21, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants