You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears to me that phpdoc-parser and wporg-developer have 2 separate ways attaching trac tickets to specific changes in the core sources:
using @link <url of trac ticket> in docblocks sources.
using the "Attach Ticket" field in the "Parsed Content" meta box when editing a wp-parser-(class|method|function|hook) post
However, to the best of my understanding at this point, neither of these methods links that ticket to a specific @since tag. Therefore, it is not possible to reliably output a trac ticket(s) for each change. Doing so would be very helpful to those writing dev-notes in the weeks leading up to a new WP release.
But that would require changes to how phpdoc-parser and/or wporg-developer stores info in the DB. If/when those changes are made to how info is stored, wp-since will need to be updated to grab that new representation.
The text was updated successfully, but these errors were encountered:
It appears to me that
phpdoc-parser
andwporg-developer
have 2 separate ways attaching trac tickets to specific changes in the core sources:@link <url of trac ticket>
in docblocks sources.However, to the best of my understanding at this point, neither of these methods links that ticket to a specific
@since
tag. Therefore, it is not possible to reliably output a trac ticket(s) for each change. Doing so would be very helpful to those writing dev-notes in the weeks leading up to a new WP release.But that would require changes to how
phpdoc-parser
and/orwporg-developer
stores info in the DB. If/when those changes are made to how info is stored,wp-since
will need to be updated to grab that new representation.The text was updated successfully, but these errors were encountered: