Skip to content
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

Cookbook example of locked-down Temporal object #603

Open
ptomato opened this issue May 20, 2020 · 3 comments · May be fixed by #1367
Open

Cookbook example of locked-down Temporal object #603

ptomato opened this issue May 20, 2020 · 3 comments · May be fixed by #1367
Assignees
Labels
documentation Additions to documentation
Milestone

Comments

@ptomato
Copy link
Collaborator

ptomato commented May 20, 2020

Follow up from #240, we need a cookbook example that does this:

Create an object that supports exactly the same interface as Temporal and is indistinguishable from it (even though side-door means such as Function.prototype.toString) except that it provides no mechanism by which code could use it to determine that the host environment is not executing within a date, time, time zone, and tzdata edition under the control of the creator, without costing the creator any capabilities provided by the native Temporal. This has use for secure environments like SES, but also for purely functional environments like Elm (cf. #103) and for testing.

This is probably best done after support for custom time zones and calendars are added to the polyfill.

@ptomato ptomato changed the title Cookbook example of Cookbook example of locked-down Temporal object May 20, 2020
@ryzokuken ryzokuken added the documentation Additions to documentation label Jun 10, 2020
@ryzokuken ryzokuken added this to To do in Finalize polyfill via automation Jun 10, 2020
@ryzokuken
Copy link
Member

Seems to be blocked on #638.

@ptomato ptomato added this to the Stable proposal milestone Sep 17, 2020
@ptomato ptomato added spec-text Specification text involved non-prod-polyfill THIS POLYFILL IS NOT FOR PRODUCTION USE! and removed non-prod-polyfill THIS POLYFILL IS NOT FOR PRODUCTION USE! spec-text Specification text involved labels Sep 18, 2020
@ptomato ptomato added this to To do in Finalize documentation via automation Oct 19, 2020
@ptomato ptomato removed this from To do in Finalize polyfill Oct 19, 2020
@ptomato
Copy link
Collaborator Author

ptomato commented Oct 19, 2020

Cookbook example to be written after the freeze and before Stage 3

@ptomato
Copy link
Collaborator Author

ptomato commented Jan 13, 2021

On further reflection the cookbook example isn't a requirement for Stage 3. To be done later.

@ptomato ptomato modified the milestones: Stage 3, Next Jan 13, 2021
@ptomato ptomato self-assigned this Feb 13, 2021
ptomato added a commit that referenced this issue Feb 15, 2021
A partial example illustrating how to deploy a Temporal object that
doesn't leak any information about the host system's clock, time zone,
locale data, or time zone data.

Closes: #603
ptomato added a commit that referenced this issue Feb 15, 2021
A partial example illustrating how to deploy a Temporal object that
doesn't leak any information about the host system's clock, time zone,
locale data, or time zone data.

Run in a separate process from the other cookbook examples.

Closes: #603
ptomato added a commit that referenced this issue Feb 17, 2021
A partial example illustrating how to deploy a Temporal object that
doesn't leak any information about the host system's clock, time zone,
locale data, or time zone data.

Run in a separate process from the other cookbook examples.

Closes: #603
@ptomato ptomato linked a pull request Feb 17, 2021 that will close this issue
ptomato added a commit that referenced this issue Feb 22, 2021
A partial example illustrating how to deploy a Temporal object that
doesn't leak any information about the host system's clock, time zone,
locale data, or time zone data.

Run in a separate process from the other cookbook examples.

Closes: #603
@ptomato ptomato modified the milestones: Next, Post Stage 4 Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Additions to documentation
Projects
Development

Successfully merging a pull request may close this issue.

2 participants