Running `screenly edge-app run --generate-mock-data` should change `mock-data.yml` when the manifest file's schema changes even if it exists

Open
#272 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

Start by running screenly edge-app run --generate-mock-data with an existing mock-data.yml, then inspect the CLI entry point for this option and how it reads screenly.yml. Trace the mock-data generation path and verify that added, removed, or modified settings are reflected in mock-data.yml without the existing-file complaint.

Written by the indexing model from the issue text.

Description

  • When screenly edge-app run --generate-mock-data runs, the CLI would complain that mock-data.yml already exists (if so).
  • For instance, if I added, deleted, or modified (e.g., updating the default value of a setting) a setting in screenly.yml. Running screenly edge-app run --generate-mock-data should modify mock-data.yml.
  • The --generate-mock-data option could be renamed to --sync-mock-data (or we could keep the former and introduce the latter as a drop-in replacement).
Dominant language
Rust
Stars
29
Forks
7
Avg merge
1d 20h
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Screenly/cli

All issues in Screenly/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.