Skip to content

Conversation

@jeremyharris
Copy link
Member

Since engines now default to falling back to the NullEngine, I felt it important to document in the Behavior Changes section of the migration docs.

configuration would fall back to writing to the ``default`` cache configuration.
If writing to the ``default`` cache configuration *also* failed in this scenario, the
engine would fall back once again to the ``NullEngine`` and prevent the application
from throwing an uncaught exception.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you include a .. versionadded:: 3.5.0 admonition here for folks using older versions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, yes!

'prefix' => 'cake_redis_',
'host' => '127.0.0.1',
'port' => 6379,
'fallback' => 'default',
Copy link
Member

@ravage84 ravage84 Jun 22, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious. What happens if one configures the same engine as fallback (e.g. by accident)? Do we have a clear exception for that? Something like "You are trying to configure the engine itself as its fallback"...

This would be a hard misconfiguration, something that SHOULD throw an exception, IMHO.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's pretty much exactly the exception it throws 😄 I did that exact thing while writing this haha

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahahaha, beautiful! 😆

@markstory markstory merged commit 2d9ce45 into cakephp:3.next Jun 22, 2017
HavokInspiration added a commit that referenced this pull request Jul 10, 2017
ryoichi-u added a commit to ryoichi-u/docs that referenced this pull request Aug 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants