Andrey Savchenko

@bobbingwide thank you for looking into it! Hadn't checked out your solution yet, but I think we are mostly done with bugs/blockers in Parser and will be moving on to...

Two separate issues: 1. Required is clearly a bug, probably unrelated to deprecated. 2. Deprecated detection for these is tricky. `_deprecated_argument()` call has no connection with _which_ argument is deprecated.

> It's trivial to determine whether an entire function is deprecated, and that's not in contention here. Yeah. the tricky part is deprecated _argument_ in a non–deprecated function.

Not picking on you, just keeping the focus clear in the thread. :) We had topics wander away before. :D

For reasonable performance we could track of touched IDs, then update post modified with one query at end of the process. Doing anything with the information probably falls on end...

If we need _anything at all_ that doesn't work with basic WP inheritance (parent/child) we are looking into Posts2Posts (I would say "relationships libraries" but there aren't... many of them)....

I totally think this should be in Parser in _some_ form. Lack of data visibility is one of the most annoying workflow issues with data-heavy projects. I consider it absolutely...

Sorry, I let this slip away from me. :( I vaguely remember someone was going to send @BoiteAWeb that export? Are you still interested in the issue? At the moment...

On the fence about templates. For now templates tags are in the process of settling in and cleaning up. Personally I am fine with leaving templates to DIY it's up...

Not so far. Honestly I think there is still depressing amount of internal cleanup to get through (which is completely stalled) before getting to figuring out generic reuse and public...