Activity Warning Log Post Sim

Open
#673 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
frontend

Research direction

No files, tests, or entry points are named. Start by locating the activity effect model and the existing error-console or simulated-activity UI flow; the work is done when an activity can communicate a non-fatal warning that is visible to the user without throwing an error.

Written by the indexing model from the issue text.

Description

feature
Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

No

Describe the feature request

I want a way to communicate a warning to the user from the effect model of an activity without throwing an error. There are situations where the user could simulate an activity which will complete but may not do what they are intending. For instance, a user could place an ECM_Power_On activity when the ecm instrument is already on. This will run, however, nothing will happen and the activity will finish in a matter of milliseconds - potentially confusing without a way to display a warning. Other cases are less obvious and would benefit from some method of logging a warning to the UI from an activity. I was thinking that a warning could be logged alongside a message which displays when hovering over a simulated activity which has logged a warning. Perhaps the activity could be colored to convey that a warning has occurred. A more simple option is having a warning console alongside the error console.

Dominant language
Svelte
Stars
42
Forks
14
Avg merge
1d 16h
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

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 NASA-AMMOS/plandev-ui

All issues in NASA-AMMOS/plandev-ui

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.