[wp-trac] [WordPress Trac] #29118: Registering rewrite rules is hard, so let's introduce remove_rewrite_rule.

[WordPress Trac]

#29118: Registering rewrite rules is hard, so let's introduce remove_rewrite_rule.
---------------------------+------------------------------
 Reporter:  ericlewis      |       Owner:
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Rewrite Rules  |     Version:
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+------------------------------

Comment (by ericlewis):

 Replying to [comment:6 danielbachhuber]:
 > It's not uncommon for me to hook expensive processes (for instance, a
 call to `get_terms()`) onto a rewrite filter because, as a developer, I
 know flushing rewrite rules only happens in contexts where it's fine for
 me to have an expensive process. I think flushing rewrite rules on every
 page load, and retaining all of the filters we have, is a non-starter.

 Can you expand on this use case?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29118#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform