Skip to content

feat(sync): say on the Remote access screen when its settings come from a newer PlayGuard - #547

Merged
JigSawFr merged 1 commit into
mainfrom
feat/newer-schema-notice
Nov 6, 2026
Merged

JigSawFr merged 1 commit into
mainfrom
feat/newer-schema-notice

Conversation

@JigSawFr

@JigSawFr JigSawFr commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

What this changes, and why

A sync.conf or link.conf written by a newer PlayGuard is read as far as understood and never written over, but the user only learned it from an English error at the next save. The Remote access status line now says it (amber), in the 15 catalogues, and docs/config.md mentions it. Squash merge.

How it was verified

make test (new cases in sync_files: newer sync.conf, newer link.conf, back to normal), check_resources.py, check_sources.py. Not run on a console; no desktop smoke: the screen is unchanged unless a newer file is present.

Screens: none

Checklist

  • make test and python3 tools/check_resources.py . pass
  • New strings are in every resources/i18n/*/playguard.json (English is fine as a placeholder)
  • A screen that changes on purpose is named on the Screens: line above
  • A change users can see is in the README or the user guide (docs/), in English and French (docs/fr/): docs/config.md only, which has no French page
  • Nothing writes the play timer while it counts down

…om a newer PlayGuard

sync.conf and link.conf written by a newer version are read as far as understood and never written over; the status line now says so in the 15 languages instead of only failing at the next save.
@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

🕹️ Preview of this pull request

No longer online (last commit 69af370): the preview goes when the pull request is closed. Merged: its changes are in main's simulator once main's build is published.

@JigSawFr
JigSawFr merged commit 3ea7c81 into main Nov 6, 2026
29 of 30 checks passed
@JigSawFr
JigSawFr deleted the feat/newer-schema-notice branch November 6, 2026 21:11

This branch was previously deployed

1 inactive deployment
github-pages — 69af370f Deployed Nov 6, 2026 by JigSawFr via deploy #1500
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.

1 participant