Context Navigation

Changes between Initial Version and Version 1 of Ticket #29107, comment 10

initial	v1
7	7	Is that enough in the wild for core to provide a helper function (like `queue_rewrite_rule_updates()` or something) that everyone can change to using instead of incorrectly deleting the option and causing this extra query to reappear?
8	8
9		Or... instead of caring if the option is empty vs. missing, is there a different approach core can take to tuck this concern under the rug, and internally add `rewrite_rules` to the `nooptions` array before it's queried independently, or something less sinister?
	9	Or... instead of caring if the option is empty vs. missing, is there a different approach core can take to tuck this concern under the rug, and internally add `rewrite_rules` to the `notoptions` array before it's queried independently, or something less sinister?