Update useSessionStorage to support strings + add new options + add useReadSessionStorage

[jonlinkens]

Fixes #335

Attempts to make useSessionStorage less opinionated in how session storage values are stored and parsed.

Changes

• Add third options argument to useSessionStorage:

  • parseAsJson: boolean - default to true, pass as false when you don't want a value to be parsed using JSON.parse. This will fix the bug I was describing where a value has been previously set as a string
  • parser: (value: string | null) => T - a custom parser if you have stored a session storage value with a custom serializer function
  • serializer: (value: T) => string - a custom serializer to store values in a format different from the default behavior of JSON.stringify

• Renamed initialValue to defaultValue for readability

• Removed undefined value support - I can't imagine a case where this is needed over just not storing the key/value in session storage + removing this decreases complexity of the hook

• Add useReadSessionStorage, similar to useReadLocalStorage

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4cf78c4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @juliencrn on Vercel.

@juliencrn first needs to authorize it.

[jonlinkens]

Going to close this as it seems this library is no longer maintained Apologies, will reopen! 😊

[jonlinkens]

I think this can now be closed as addressed in #439? I'll leave open so you can confirm - Thank you very much btw!

[juliencrn]

I think this can now be closed as addressed in #439? I'll leave open so you can confirm - Thank you very much btw!

Yes indeed! Your PR was good, I, unfortunately, worked on it before seeing your one.
I will add you to the contributor list, Thank you 👍

[jonlinkens]

I, unfortunately, worked on it before seeing your one

No worries at all, just happy to see the bug fixed - thanks for your hard work on this library

[erichartline]

Any chance that we could still bring in the useReadSessionStorage hook from this PR? We have the equivalent for localStorage but not sessionStorage.