Skip to content

fix depending results after changing value of "entry->isRead"#4331

Merged
Alkarex merged 3 commits intoFreshRSS:edgefrom
cn-tools:edge
Apr 26, 2022
Merged

fix depending results after changing value of "entry->isRead"#4331
Alkarex merged 3 commits intoFreshRSS:edgefrom
cn-tools:edge

Conversation

@cn-tools
Copy link
Copy Markdown
Contributor

Changes proposed in this pull request:

  • if anybody use the hook 'entry_before_insert' and change the value of the property 'entry->isRead', the depending results are correct now.
  • In my case my config let all new entrys as "isRead=FALSE" as i will. A new extension which is in progress, can/should/must change the value of this property, but the depending results of this property are wrong before this fix.

Pull request checklist:

  • clear commit messages
  • code manually tested
  • unit tests written (optional if too hard)
  • documentation updated

…of hook 'entry_before_insert'

if anybody use the hook 'entry_before_insert' and change the value of the property 'entry->isRead', the depending results are correct now.

In my case my config let all new entrys as "isRead=FALSE" as i will. A new extension which is in progress, can/should/must change the value of this property, but the depending results of this property are wrong before this fix.
@Alkarex Alkarex added this to the 1.20.0 milestone Apr 25, 2022
@Alkarex
Copy link
Copy Markdown
Member

Alkarex commented Apr 25, 2022

Thanks, looks reasonable (besides my little suggestion)

@cn-tools
Copy link
Copy Markdown
Contributor Author

Thanks! And i think you are right with your suggestion, so i merged it in.

@Alkarex Alkarex merged commit 046598e into FreshRSS:edge Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants