Skip to content

[11.x] document new cache driver #10032

New issue

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

Closed
wants to merge 319 commits into from

Conversation

browner12
Copy link
Contributor

documentation for this PR.

should not be merged until after next release so my bugfix is in there and it actually works.

I struggled with the wording on this. maybe it'd be better to just show an example config/auth.php entry?

@taylorotwell
Copy link
Member

taylorotwell commented Nov 19, 2024

Before we document this could we implement that automatic hashing of the keys so we don't need to worry about prefixes @browner12?

@taylorotwell taylorotwell marked this pull request as draft November 19, 2024 22:32
@browner12
Copy link
Contributor Author

@taylorotwell was that suggested somewhere? I'm not seeing it.

Also, I'm a little confused. Are you suggesting to hash the "prefix.email" combo? How would we retrieve it from the cache then?

AhmedAlaa4611 and others added 27 commits March 13, 2025 10:09
* [12.x] Document `increment` and `decrement`

* formatting

* Update context.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
Co-authored-by: John Rivs <hi@johnrivs.com>
* Add documentation for getChanges

The eloquent method getOriginal is already documented, and we should do the same with getChanges.

* Update eloquent.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Explain redirectUsersTo functionality

* formatting

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* fix: improve workOs docs

* Update starter-kits.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Improve anticipate method example

* wip

* Update artisan.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
….3) (laravel#10266)

* Update Symfony link in artisan.md

* Update artisan.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Add `ddBody` to http-tests.md

* Update http-tests.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
in the framework, we are usign a single indent on new lines, so this mirrors that in the docs
* Add schedule useCache example

* formatting

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
…upgrade guide (laravel#10271)

* Add DatabaseTokenRepository constructor signature update to 12.x upgrade guide

* formatting

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
CedzyC and others added 26 commits June 17, 2025 08:19
* Added Passport import to "Overriding Default Models"

* Update passport.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* FailOnException middleware

* Update queues.md

* Update queues.md

* formatting

* wip

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
Clarify env() behavior after configuration caching
The current documentation states that “all calls to the env function will return null” once the configuration has been cached.

However, this is only true for environment variables defined exclusively in the .env file.

If the environment variable exists at the system level (e.g., via putenv(), server configuration, env() will still return a value after caching.

This clarification helps developers understand that env() is not completely disabled after config:cache, but rather depends on the source of the environment variable.
* Add documentation for Str::of(...)->fromBase64()

* Add documentation for Str::of(...)->fromBase64()

* Apply suggestions

Co-authored-by: Sebastian Hädrich <11225821+shaedrich@users.noreply.github.com>

* formatting

---------

Co-authored-by: Sebastian Hädrich <11225821+shaedrich@users.noreply.github.com>
Co-authored-by: Taylor Otwell <taylor@laravel.com>
`skip()` and `take()` are alias methods to `offset()` and `limit()`. IMO we should only use and document the main methods, not the aliases.  This will encourage more performant coding, just like we now do in `laravel/framework`.

IF it's decided we still want to mention the aliases, I'd recommended listing them second as the alternatives.  I can make that change if desired.
…s and consistency (laravel#10525)

* Update frontend.md

* Update vite.md
* Add the failed method to queued mailables.

* formatting

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Add proper links

* Update helpers.md

---------

Co-authored-by: Taylor Otwell <taylor@laravel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.