Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
We've made some progress since this question was posted, but there is still work to do (especially in the case of deleted answers). Edits to questions and closures are more specific (I assume reop...
Answer
#2: Post edited
by
Monica Cellio
·
2023-01-13T14:19:23Z (almost 2 years ago)
also address new answers
- We've made some progress since this question was posted, but there is still work to do (especially in the case of [deleted answers](https://meta.codidact.com/posts/287712)). Edits to questions and closures are more specific (I assume reopens are but can't find an example to confirm). New answers, edits to answers, and answer deletions still show the generic "last activity". [This issue is on our roadmap](https://github.com/codidact/qpixel/issues/315) but we haven't been able to work on it yet. I'm sorry it's taking this long.
I think the issues with answers -- both edits and deletions -- is that the code is checking the question (top-level post, really) state to generate the text on the category list, and the question itself doesn't record activity on answers. For deleted answers, I think if we recorded "answer deleted" (with a link for those who can see) in the question history, then we could use that information and people who can't see deleted posts would not be as confused. Answer edits are probably a little more complicated because that does require that the query check all the answers (in a performant way), but yes we want this.
- We've made some progress since this question was posted, but there is still work to do (especially in the case of [deleted answers](https://meta.codidact.com/posts/287712)). Edits to questions and closures are more specific (I assume reopens are but can't find an example to confirm). New answers, edits to answers, and answer deletions still show the generic "last activity". [This issue is on our roadmap](https://github.com/codidact/qpixel/issues/315) but we haven't been able to work on it yet. I'm sorry it's taking this long.
- I think the issues with answers -- both edits and deletions -- is that the code is checking the question (top-level post, really) state to generate the text on the category list, and the question itself doesn't record activity on answers. For deleted answers, I think if we recorded "answer deleted" (with a link for those who can see) in the question history, then we could use that information and people who can't see deleted posts would not be as confused. New answers could also reasonably be added to the question history; this would also help sort out the sequence when question edits and new answers interact with each other and we need to know which happened first. Answer edits are probably a little more complicated because that does require that the query check all the answers (in a performant way), but yes we want this.
#1: Initial revision
by
Monica Cellio
·
2023-01-13T14:15:33Z (almost 2 years ago)
We've made some progress since this question was posted, but there is still work to do (especially in the case of [deleted answers](https://meta.codidact.com/posts/287712)). Edits to questions and closures are more specific (I assume reopens are but can't find an example to confirm). New answers, edits to answers, and answer deletions still show the generic "last activity". [This issue is on our roadmap](https://github.com/codidact/qpixel/issues/315) but we haven't been able to work on it yet. I'm sorry it's taking this long. I think the issues with answers -- both edits and deletions -- is that the code is checking the question (top-level post, really) state to generate the text on the category list, and the question itself doesn't record activity on answers. For deleted answers, I think if we recorded "answer deleted" (with a link for those who can see) in the question history, then we could use that information and people who can't see deleted posts would not be as confused. Answer edits are probably a little more complicated because that does require that the query check all the answers (in a performant way), but yes we want this.