-
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
Fix: Move search count from cookie to local storage #48
Comments
Hello, @gsambrotta and @ElliotForWater/elliotforwater-core-dev! I've been newly acquainted with your project and would love to help! Are you still working on this issue? If so, I'd be happy to take it on. |
Hi @KitanGarcia Thank you for your interest in contributing to Elliot for Water. Any pro or cons you see in these solutions? |
Thanks for the response, @gsambrotta . After doing some research on my end, I do think that going with LocalStorage is the best way to go about things, due to exactly what you've mentioned. Unfortunately, I'm actually unable to get the project running at the moment. It must be some rookie mistake on my part somewhere. I'm following this link: https://github.com/ElliotForWater/elliotforwater.com/wiki/1.-Set-up-and-usage After cloning and entering the repo, I ran: I got an error pertaining to env-cmd, so I tried some suggestions on stack overflow (running different commands and using -e instead of -f), and also installed env-cmd globally. I have not modified the dev script in package.json at all. When I run |
@KitanGarcia The |
@gsambrotta Just to clarify, you just want the search count to be moved to local storage, correct? The rest of the cookies stay as cookies and do not be made part of local storage? |
Yes, for the moment we can move just the search count. Then we can see later about the other cookies. Thanks @KitanGarcia |
We are considering saving search count to localStorage instead of cookies mostly to not have an expiration date.
Everything else should stay the same.
Happy to hear feedbacks about that.
The text was updated successfully, but these errors were encountered: