Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to mark issues as read #640 #645

Merged
merged 19 commits into from
May 29, 2015
Merged

Add ability to mark issues as read #640 #645

merged 19 commits into from
May 29, 2015

Conversation

dariusf
Copy link
Contributor

@dariusf dariusf commented May 29, 2015

dariusf added 19 commits May 29, 2015 11:51
We need two fields to track read status: we can't just clear the
marked-as-read status upon an issue being updated because we want to
indicate which of its events are new.
The problem is that we set the the read status of issues in
MultiModel::add instead of MultiModel::addPending. The first happens on
every change to the model, including updates, whereas the second happens
only when a new model is added.

The fix is to move it to addPending: that's the only time we should
reset the read status of an issue to what is in Preferences.
Bugs:

- On refreshing a panel with an updated filter, all the events and
  comments would disappear before being loaded again
- After marking an issue as read, markedReadAt was cleared

The cause was that all transient state (metadata, read status) was not
being transferred when issues were updated. This was due to TurboIssues
being constructed from new external Issue objects that were created as
part of the update process.

The fix is to explicitly ensure that transient state is transferred.
This is if they occurred before an issue was marked as read.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 22.3% when pulling 75a65eb on Issue640 into 0a94667 on master.

@dariusf dariusf merged commit 75a65eb into master May 29, 2015
@dariusf dariusf deleted the Issue640 branch May 29, 2015 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants