Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

66%
+2 −0
Meta Filtering the sandbox for ease of feedback

"Finalized" (or "cancelled") seems like it should be a property of the post. We can close questions -- but not articles. I think that was a change at some point, because the point of closing is t...

posted 2y ago by Monica Cellio‭  ·  edited 2y ago by Monica Cellio‭

Answer
#3: Post edited by user avatar Monica Cellio‭ · 2022-10-26T00:31:59Z (about 2 years ago)
  • "Finalized" (or "cancelled") seems like it should be a property of the post. We can *close* questions -- but not articles. I think that was a change at some point, because the point of closing is to say "no more answers" and articles don't have answers to begin with, so what does it mean to close one? But maybe we need to bring that back in some form?
  • With the forthcoming filters feature, you'll be able to use question status (open, closed, duplicate) in filter rules. If we wanted articles to have status too, what should the options be?
  • Another option: in the discussion of [this request for cross-category duplicate closure](https://github.com/codidact/qpixel/issues/698), I proposed that articles could have a single close option, "duplicate".
  • If we made one of those changes to the code, then there would be a way to change the state of articles in a filterable way. I'm going to ask the team about the feasibility of cross-category duplicates, which would help here, but I can't make any promises since I can't just go write the code myself.
  • "Finalized" (or "cancelled") seems like it should be a property of the post. We can *close* questions -- but not articles. I think that was a change at some point, because the point of closing is to say "no more answers" and articles don't have answers to begin with, so what does it mean to close one? But maybe we need to bring that back in some form?
  • With the forthcoming filters feature, you'll be able to use question status (open, closed, duplicate) in filter rules. If we wanted articles to have status too, what should the options be?
  • Another option: in the discussion of [this request for cross-category duplicate closure](https://github.com/codidact/qpixel/issues/698), I proposed that articles could have a single close option, "duplicate".
  • If we made one of those changes to the code, then there would be a way to change the state of articles in a filterable way. I'm going to ask the team about the feasibility of cross-category duplicates, which would help here, but I can't make any promises since I can't just go write the code myself.
  • --
  • Followup: I've [posted on Meta about closing articles, current limitations, and hopes & dreams](https://meta.codidact.com/posts/283920/287316#answer-287316).
#2: Post edited by user avatar Monica Cellio‭ · 2022-10-14T01:47:15Z (about 2 years ago)
found a related issue
  • "Finalized" (or "cancelled") seems like it should be a property of the post. We can *close* questions -- but not articles. I think that was a change at some point, because the point of closing is to say "no more answers" and articles don't have answers to begin with, so what does it mean to close one? But maybe we need to bring that back in some form?
  • With the forthcoming filters feature, you'll be able to use question status (open, closed, duplicate) in filter rules. If we wanted articles to have status too, what should the options be?
  • "Finalized" (or "cancelled") seems like it should be a property of the post. We can *close* questions -- but not articles. I think that was a change at some point, because the point of closing is to say "no more answers" and articles don't have answers to begin with, so what does it mean to close one? But maybe we need to bring that back in some form?
  • With the forthcoming filters feature, you'll be able to use question status (open, closed, duplicate) in filter rules. If we wanted articles to have status too, what should the options be?
  • Another option: in the discussion of [this request for cross-category duplicate closure](https://github.com/codidact/qpixel/issues/698), I proposed that articles could have a single close option, "duplicate".
  • If we made one of those changes to the code, then there would be a way to change the state of articles in a filterable way. I'm going to ask the team about the feasibility of cross-category duplicates, which would help here, but I can't make any promises since I can't just go write the code myself.
#1: Initial revision by user avatar Monica Cellio‭ · 2022-10-14T01:31:51Z (about 2 years ago)
"Finalized" (or "cancelled") seems like it should be a property of the post.  We can *close* questions -- but not articles.  I think that was a change at some point, because the point of closing is to say "no more answers" and articles don't have answers to begin with, so what does it mean to close one?  But maybe we need to bring that back in some form?

With the forthcoming filters feature, you'll be able to use question status (open, closed, duplicate) in filter rules.  If we wanted articles to have status too, what should the options be?