docs - createCookieSessionStorage says commitSession not needed about remix HOT 3 OPEN

Yes, the documentation needs to be corrected. For the session API, all session storage providers require you to call commitSession after mutation.

I think what the documentation was alluding to was you don't have to return a set-cookie header in the response after every commit, just the initial one.

In cookie session storage, the session data is stored entirely in the cookie, so any changes require you to send an updated cookie via the set-cookie header.

However, in other storage providers like Cloudflare KV or file-based sessions, the only thing stored in the cookie is the session ID. You would send that id in the set-cookie header on creation. The session ID is used to look up the session in the storage. Since the session id never changes, you don't need to keep sending a set-cookie header.

from remix.

@kiliman thanks, I raised a PR here along those lines. Let me know if you have a suggestion on wording
#9445

from remix.

Might be related with this issue? Its about memory / custom storage, but looks like same sort of problem with the behavior and documentation:
#9338

from remix.