---
# System prepended metadata

title: Remove EventGroup
tags: [pitch]

---

---
robots: noindex, nofollow
tags: pitch
---
For instructions on shaping a project see here: [Shaping a Project](/kX02SXVbS6KzMOQd56i6Cg)

# Remove EventGroup
:snail: 
### Problem
*From: [Problem guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-1-problem)*
EventGroup which has been targeted for removal. `EventGroup` adds unnecessary cycles to event handling. There are still several places where EventGroup appears to be used to raise events which may cause complications. Additionally there are several high value components like Details list which rely on EventGroup. These last complications make replacing EventGroup with native eventing more difficult. There will need to be a resonable solution brought forward to handle

1. Custom eventing for controls like `Selection`
2. Components that expose an argument with a type `EventGroup`
3. Removing EventGroup from something details list needs to be tested more than it might be otherwise.


### Appetite
*From: [Appetite guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-2-appetite)*
2 weeks, this is mainly about research and prototyping. The end goal is to have a possible solution for each of those problems

### Solution
There should be a shaped project or suggestion for each of the 3 problems above.

### Risks (Rabbit holes)
*From: [Rabbit hole guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-4-rabbit-holes)*

1. There likely won't be a right answer.
2. There are some parties that care fairly deeply about the Details list and related components, it will be important to engage them, and they could be a blocker

### Out of scope (No-gos)
*From: [No-gos guidance](https://basecamp.com/shapeup/1.5-chapter-06#ingredient-5-no-gos)*

Implementing a full fix is out of the scope for this particular project.