EFForg / EFForg/rayhunter

Extract shared components for GUI

Open
#1,144 0 comments 0 reactions 1 assignee Claimed by @untitaker View on GitHub
maintenance ui
Dominant language
Rust
Stars
5.8k
Forks
490
Avg merge
3d 10h
Merged PRs (30d)
23

Description

Our UI could be DRY-ed in a bunch of different ways:

* We need to start extracting common UI components. When we add a new heuristic we end up copypasting the same 20 tailwind classes for the config form. #1138
* We should reuse components across installer and the daemon UI.
* For this we need to put them into a shared npm workspace. This should also halve the amount of dependabot security PRs as there's just one lockfile. #1143
* Our config form could use a refactor so that the list of available heuristics is fetched from the backend. It shouldn't be necessary to write your own checkbox for a heuristic into the frontend code. We already load heuristic metadata from the backend when showing enabled heuristics for a recording.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.