Skip to content
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

feat: cache s key prefix configuration #666

Merged
merged 5 commits into from May 9, 2024

Conversation

ezerdemello
Copy link
Contributor

Please check if the PR fulfills these requirements

  • [x ] Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Includes new configuration option for create cache's keys prefix if this option is informed. If this new configuration option didn't setup nothing happens.

@jaredwray
Copy link
Owner

@ezerdemello thanks for the pull request. I would recommend you add this value to options instead of adding another.

@ezerdemello
Copy link
Contributor Author

ezerdemello commented Apr 22, 2024 via email

@jaredwray
Copy link
Owner

@ezerdemello - great. Let me know when the change is ready.

@ezerdemello
Copy link
Contributor Author

ezerdemello commented Apr 24, 2024 via email

@jaredwray
Copy link
Owner

@ezerdemello - There are two things we need. The main thing is we need to get a unit test to validate this. Can you submit that? if you do I can add in the documentation for this.

Thanks!

@zph
Copy link

zph commented May 3, 2024

This will be a nice addition @ezerdemello @jaredwray , I found myself implementing this in a custom store and having it baked into the interface will be superior. 🙇

@jaredwray
Copy link
Owner

@ezerdemello and @zph - Agreed and the last updates I can do if they arent done earlier in a week or so then will deploy.

@jaredwray jaredwray merged commit 734e8b0 into jaredwray:main May 9, 2024
3 checks passed
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.

None yet

4 participants