-
Notifications
You must be signed in to change notification settings - Fork 13
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
Feature: Ability to assert something exists (or not) in cache #3
Comments
It is up to you to figure it out and implement it. |
Oh right I thought this module was maintained |
I can merge your pull request and release a new version, but we haven't had a regular Laravel expert for a few years. |
I'm happy to maintain this module if you like, been using Laravel daily
since v3
…On Thu, 2 Jan 2020, 8:49 pm Gintautas Miselis, ***@***.***> wrote:
I can merge your pull request and release a new version, but we haven't
had a regular Laravel expert for a few years.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/Codeception/module-laravel5/issues/1?email_source=notifications&email_token=AAB52NJNBBA2UMCI3XYBKPDQ3ZHNFA5CNFSM4KCFCK72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH7LYEY#issuecomment-570342419>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB52NL4JSZF2ORIIUZXQDDQ3ZHNFANCNFSM4KCFCK7Q>
.
|
@Jamesking56 are you still interested in submitting a PR for this new feature? If so, please follow the contribution guide. As long as you can verify that it works in the test project and you can document the method, I will gladly help you get it merged. Also note that Cheers! |
Hello,
Would be really useful if there was a way to ensure (or not) that something existed in Laravel's cache.
I want to make sure that certain things are cached correctly when doing functional tests.
The text was updated successfully, but these errors were encountered: