grafana/k6-studio

k6 Studio use default settings as fallback without informing the user

Open

#567 opened on Mar 14, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (27 forks)auto 404
good first issue

Repository metrics

Stars
 (510 stars)
PR merge metrics
 (PR metrics pending)

Description

Steps to reproduce the problem

I don't know the exact steps, but I've stumbled upon it multiple times during development. Perhaps, saving a copy of your settings file and intentionally corrupting it may work?

In any case, when the file cannot be parsed, the default values will be used instead (incl. usage reporting preference)

Expected behaviour

The user should be informed about using default settings as a fallback.

Currently, It's also technically possible to access settings in code before the settings file is loaded. Consider improving the approach for loading settings to prevent this.

Actual behaviour

Default settings are used, but it may not be clear to the user.

Grafana k6 Studio version

any

OS

any

Contributor guide

Research direction
Improve the settings loading mechanism to detect when the settings file cannot be parsed and show a notification or warning to the user. Also ensure that settings are loaded before any code accesses them to avoid using defaults inadvertently.
Tech stack
typescript
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60