[12.x] Add milliseconds, weeks, and months duration helpers to Illuminate\Support
#57997
+40
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds three missing duration helpers to
Illuminate\Support:milliseconds(),weeks(), andmonths().They return
CarbonIntervalinstances, matching the existingseconds,minutes,hours,days, andyearshelpers.Why?
These units are commonly used when working with cache TTLs, scheduled tasks, HTTP client timeouts, retry delays, and time-based tests.
While developers can call
CarbonInterval::milliseconds()directly, Laravel already standardizes duration helpers as a more readable and consistent API.Benefits
function_exists)Edit:
Also added
microseconds. I think this is needed less often, but sincemillisecondsonly supports anintvalue, it will be useful for the project that this PR was created for, since we currently pass a float toCarbonInterval::milliseconds(), which is supported and has the desired effect, despite the docblock only notatingintas value in CarbonInterval.I would also be open to letting
milliseconds()accept aint|float, which will probably remove the need formicroseconds()for most people