search

laravel / ideas

Issues board used for Laravel internals discussions.
939 stars 28 forks source link

Document "version added" for functionality that was added in a minor version #2592

Closed apokryfos closed 3 years ago

apokryfos commented 3 years ago

I recently saw this question in StackOverflow which was asking why a feature that was in the 8.x documentation did not exist. I've seen similar questions before about this (last one was about upsert if I recall correctly).

I think it would be helpful, if a feature is not shipped when the major version is released but rather added in a minor version, to note this in the documentation since it might save some development time (and more importantly) might provide motivation/reminder to always use the latest minor version.

ahinkle commented 3 years ago

Feel free to open a PR; they are open source. 👍

apokryfos commented 3 years ago

While I can open a PR for this specific case, how can we enforce this happens every time a new feature is added to the documentation under e.g. version 8.x but is only available after e.g. version 8.40 or something like that? What I'm suggesting is more of a "Todo" for anyone updating the documentation to add the version available when they are documenting a new feature added in this way.

apokryfos commented 3 years ago

Based on the comment in https://github.com/laravel/docs/pull/7120 PRs for this sort of change are not welcome as the assumption is always using the latest Laravel version.