You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did a search to see if there is a similar issue or if a pull request is open.
Is your feature request related to a problem?
For me, the very next event would be enough as any subsequent trash collections are not that important to me. But the card always shows a minimum of one event per template. In addition, the card takes quite some space from the dashboard. I would prefer a smaller card that is more discreet overall.
Describe the solution you'd like
I would like to have an option to limit the card to display just one, i.e. the very next trash collection. In addition, space can be saved as a smaller card with just one event could be embedded into the space of a standard tile card. This would also support the design of the new sections view.
So I suggest a switchable option such as Show next event only.
Describe alternatives you've considered
This feature request goes in a similar direction and would achieve the same result.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Requirements
Is your feature request related to a problem?
For me, the very next event would be enough as any subsequent trash collections are not that important to me. But the card always shows a minimum of one event per template. In addition, the card takes quite some space from the dashboard. I would prefer a smaller card that is more discreet overall.
Describe the solution you'd like
I would like to have an option to limit the card to display just one, i.e. the very next trash collection. In addition, space can be saved as a smaller card with just one event could be embedded into the space of a standard
tile
card. This would also support the design of the new sections view.So I suggest a switchable option such as
Show next event only
.Describe alternatives you've considered
This feature request goes in a similar direction and would achieve the same result.
Additional context
No response
The text was updated successfully, but these errors were encountered: