Skip to content

RFC: Timeline event packing #1878

@Avamander

Description

@Avamander

Problem:
It's somewhat difficult to handle long-term and short-term events overlapping in the timeline in user-facing situations.

Proposal:
Some of this confusion can be removed by implementing predictable conflict resolution.

We can adjust the timestamp value of the longer event to start at the end of shorter/previous element's timestamp + expiration and shorten expiration of the longer event by the amount shortened.

This packing shouldn't be done for equally-long events, neither should a shorter event be shortened.

Before:

|     |     |     |     |     |     |     |     |     |
|────────────────────────────────────────────────────────────►
  ┌───────────┐
  │Temperature│
  └───────────┘
     ┌────────────────────────────────────────────────┐
     │ Temperature (long-term)                        │
     └────────────────────────────────────────────────┘

After:

|     |     |     |     |     |     |     |     |     |
|────────────────────────────────────────────────────────────►
  ┌───────────┐┌──────────────────────────────────────┐
  │Temperature││ Temperature (long-term)              │
  └───────────┘└──────────────────────────────────────┘

Are there any potential use-cases where this might not work out as intended?

Metadata

Metadata

Assignees

No one assigned

    Labels

    weatherBugs and PRs related to Weather

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions