WordPress.org

Making WordPress.org

#1889 closed defect (invalid)

Inaccurate listings for @since tags

Reported by: johnbillion Owned by:
Milestone: Priority: normal
Component: Developer Hub Keywords:
Cc:

Description

If you view the list of functions introduced in 4.5, you'll see functions that are older than that but which have a @since entry indicating a change made to the function in 4.5. For example, wp_normalize_path(), which was introduced in 3.9 but has changes listed for 4.4 and 4.5.

 * @since 3.9.0
 * @since 4.4.0 Ensures upper-case drive letters on Windows systems.
 * @since 4.5.0 Allows for Windows network shares.

Change History (2)

This ticket was mentioned in Slack in #meta-devhub by drew. View the logs.


17 months ago

#2 @coffee2code
16 months ago

  • Resolution set to invalid
  • Status changed from new to closed

The 'since' view was never intended to list functions introduced in a given release. It is meant to list functions added or updated in a given release (that is to say, those that have a @since entry for that release).

On the code reference landing page that's why the widget is labeled "New and Updated in WordPress X.Y" instead of just "New in...".

While the desire to find functions, etc introduced in a given WP release is reasonable, it wasn't feasible for consideration until recently since the @since tag wasn't always present for a reasonable majority of functions. (I believe it was only through an effort within the last couple of years that many functions saw an @since added for their introduction to the codebase.)

Anyhow, the 'since' view has been this way for years so it's best not to change what it represents. I'd advocate making a separate ticket to request introduction of the ability to view functions, etc introduced in a given release. It'd likely entail creating a new taxonomy. (@since is its own taxonomy, but it'd be hairy to get only the posts that have a @since for a given version but not any earlier version).

Note: See TracTickets for help on using tickets.