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

how can I store key and value without any modification like md5? #53

Closed
matiazar opened this issue Jan 16, 2024 · 5 comments
Closed

how can I store key and value without any modification like md5? #53

matiazar opened this issue Jan 16, 2024 · 5 comments

Comments

@matiazar
Copy link

Laravel Settings

v3

Laravel Version

v10

Bug description

how can I store key and value without any modification like md5?
please.

Steps to reproduce

No response

Relevant log output

No response

@matiazar matiazar added the bug Something isn't working label Jan 16, 2024
@matiazar
Copy link
Author

I found how to disable decryotion.. now I need to disable serialization. I need only a value. thanks

@rawilk
Copy link
Owner

rawilk commented Jan 21, 2024

Please refer to the docs for this.

There is already a built-in key generator, called the ReadableKeyGenerator, that will not use md5 on the setting keys. You just need to configure the package to use this one instead in the config file.

@rawilk rawilk removed the bug Something isn't working label Jan 21, 2024
@matiazar
Copy link
Author

yes I used it,. but now I want to make the value clean.. store the value I send.. only text or number

thanks

@rawilk
Copy link
Owner

rawilk commented Jan 26, 2024

What do you mean by "make the value clean"? If you don't want the value encrypted, you can disable that in the config. You can also use a custom value serializer, similar to how the key generators work, to prevent the value from being serialized or json_encoded before storing it.

@rawilk
Copy link
Owner

rawilk commented Mar 10, 2024

I'm going to close this issue since it hasn't had any activity in a while. Feel free to re-open in the future if necessary.

@rawilk rawilk closed this as completed Mar 10, 2024
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

No branches or pull requests

2 participants