bento
bento copied to clipboard
Split bento library in two, core and extra library
Proposal
It seems the bento library is getting clogged by classes that correspond to a specific use case.
For readability, we could split the library in two, and publish two artifacts.
One would be the core library, which only contains what is necessary for bento to work: small, concise, would contain the content of the core package.
Anything else, like the paginationlistcomponent, nested component, list component... could be splitted in a different library.
Why?
It feels that a bunch of the component that we include extra are quite opinionated:
- The list component by default displays separators.
- The SimpleComponent takes a presenter but no items? (It will return the presenter, but always null for the item)
- ... and more
These opinion are diluating the simplicity of Bento.