Significant-Gravitas/AutoGPT

Show disabled blocks as disabled (greyed out and un-selectable) in the block list with a reason on hover (or similar) and add a separate block bool to hide blocks from the list

Open

#8,889 opened on Dec 5, 2024

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Python (184,310 stars) (46,237 forks)batch import
fridgegood first issue

Description

Right now, locally, it's challenging to know what blocks exist and what blocks you don't have configured vs. what blocks don't exist. Add this capability so we can still hide blocks on the platform. You may need to play with the wording of hide vs disabled, etc

Contributor guide

Tech stack
python
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
45
Research direction
Examine the frontend block list component in the AutoGPT repository (likely in a Python/JS framework like React or similar). Identify where blocks are fetched and rendered. Explore how to add a disabled state (greyed out and un selectable) and a tooltip with the reason. Consider adding a separate boolean to hide blocks from the list. Review any existing discussion or comments in the issue for guidance on terminology.