Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

frontend: provide a consolidated page of Action triggers #1539

Open
1 task done
ES-Alexander opened this issue Jan 6, 2025 · 0 comments
Open
1 task done

frontend: provide a consolidated page of Action triggers #1539

ES-Alexander opened this issue Jan 6, 2025 · 0 comments
Labels
Actions enhancement New feature or request ui UI related issues

Comments

@ES-Alexander
Copy link
Contributor

ES-Alexander commented Jan 6, 2025

Current behaviour

Joystick buttons and Input Button widgets can both trigger Actions, Actions can potentially call other Actions, and #1538 may add more widget-based triggers. That's starting to get quite fragmented, so it could become tricky to determine where a given Action is being triggered from.

Expected or desired behaviour

  • Action calls (and responses) should be included in the Cockpit system logs (if they aren't already)
    • Ideally this should include some reference to what source called them (e.g. a widget or Action name)
  • An extra tab in Settings / Actions that specifies all known Action triggers would be handy
    • Ideally this would include some basic parsing of custom JS Actions to see whether they call other Actions

Prerequisites

  • I have checked to make sure that a similar request has not already been filed or fixed.
@ES-Alexander ES-Alexander added enhancement New feature or request ui UI related issues Actions labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Actions enhancement New feature or request ui UI related issues
Projects
None yet
Development

No branches or pull requests

1 participant