Expose environment ids?
Open
Nobody has claimed this yet.
TPAC2025
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Now that we have IDs to identify environments, perhaps environments should have access to them too? E.g. might be useful for sites that allow different session per open document.
Also, we should probably say that environment ids should be unique per origin, but should not be globally unique or something like that, so they can not really be used as additional entropy to identify the user.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the environment-ID behavior described in the issue and clarify the API and origin-uniqueness requirements; done means an agreed specification for exposing IDs and their privacy scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100