expressjs/session

use proxies for session data

Open

#46 opened on May 29, 2014

View on GitHub
 (17 comments) (0 reactions) (0 assignees)JavaScript (6,073 stars) (977 forks)batch import
enhancementhelp wanted

Description

So that we can check that the store actually exists (#4) and whatever else we want.

req.session.set('thing.property', stuff)

req,session.get('thing.property')

Would be removed of favour of Proxies, eventually. In like a decade when they actually land.

A big issue would be people being idiots and assigning stuff onto the data object or get()-ed objects.

Contributor guide

Tech stack
javascript
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
understanding of JavaScript Proxies
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue proposes using JavaScript Proxies for session data to allow dynamic property access. However, the issue is from 2014 and is not currently actionable. No linked PRs or recent comments. Contributors should first check if the maintainers have discussed this elsewhere. The implementation would require modifying the session store to use Proxy objects, ensuring backward compatibility, and handling edge cases.