Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.76%. Comparing base (1583183) to head (1ba295a).

@@           Coverage Diff           @@
##             main    #1819   +/-   ##
=======================================
  Coverage   81.76%   81.76%           
=======================================
  Files          35       35           
  Lines        7742     7742           
  Branches      316      316           
=======================================
  Hits         6330     6330           
  Misses       1400     1400           
  Partials       12       12           

are we wanting to export types in this granular way in most cases?

@zimeg Great question; I don't think so, and I would personally default to keeping things internal/non-exported, at least as an initial move, because:

1. It's easier to put something out there than it is to retract; adding something new is additive while taking something away is a breaking change.
2. In terms of TS specifically, it can be harder to know and manage what is unused if we just export everything.
3. In this particular case, we specifically had a request from the community to export this particular type; see this OP in Add Timepicker to @slack/types #1226:

Moving union types to their own exported types. For example, elements supported within the ActionsBlock having a type of ActionsElements. For SectionBlock, SectionElements. Etc.

Of course always open to discussing and changing this inclination if the team feels otherwise.