Replies: 1 comment 1 reply
|
The timeline represent a somewhat processed view of the changes. You can think of it as what would be shown in a bug timeline on github. It's similar as the raw data but easier to display for a UI, ie without having the "business logic". |
1 reply
|
Ah - so the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to understand the relationship between a
bug'sOperations and the cachedTimeline. It's pretty clear that everyOperationrepresents a change to thebug(well - I managed to create a bunch that don't actually accomplish this), but the first operation sets thetitleand creates the firstcomment, but I only see that thecommenthas been changed in thetimeline. This is an example but is caused here:git-bug/entities/bug/op_create.go
Lines 56 to 60 in 7468b37
Other
Operations don't append to theTimelineat all. What should and shouldn't be represented in theTimeline?All reactions