We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A follow up for briannesbitt/Carbon#2966 and briannesbitt/Carbon#3017
Proposal: bring back old behavior as new methods createFromTimestampCurrentTZ() and createFromTimestampMsCurrentTZ()
This behavior was too useful to ignore and having a more explicit name for it would make it more semantic
The text was updated successfully, but these errors were encountered:
Hello, what's the benefit over passing date_default_timezone_get() as a second parameter?
date_default_timezone_get()
Sorry, something went wrong.
Your call of course, I'm just suggesting
No branches or pull requests
A follow up for briannesbitt/Carbon#2966 and briannesbitt/Carbon#3017
Proposal: bring back old behavior as new methods createFromTimestampCurrentTZ() and createFromTimestampMsCurrentTZ()
This behavior was too useful to ignore and having a more explicit name for it would make it more semantic
The text was updated successfully, but these errors were encountered: