microsoft/Terminal

UX for different StartupTaskState

Open

#6,254 opened on May 29, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (3,212 forks)batch import
Area-UserInterfaceHelp WantedIssue-TaskProduct-Terminal

Repository metrics

Stars
 (35,764 stars)
PR merge metrics
 (Avg merge 27d 19h) (24 merged PRs in 30d)

Description

I feel like for this (and the other StartupTaskState) we should display a warning of some sort. But I'd be ok with just ignoring these cases for now and linking a new GitHub issue for a separate PR.

Originally posted by @carlos-zamora in https://github.com/microsoft/terminal/pull/4908

Additional context:

Specifically, StartupTaskState::DisabledByUser is the primary case to handle. The value of displaying feedback to users for the other states could be debated; I'm not aware of other applications that pop a dialog or feedback when the "start application on windows start" checkbox or whatnot is changed, but those applications generally don't have users managing settings via Notepad :)

Contributor guide

Research direction
Inspect the settings UI code in Terminal to find where StartupTaskState is handled and add a warning dialog for DisabledByUser state.
Tech stack
cpp
Domain
desktop
Issue type
Feature
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75