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

std:test for testing infra implementations #17

Open
hiroshige-g opened this issue May 4, 2018 · 0 comments
Open

std:test for testing infra implementations #17

hiroshige-g opened this issue May 4, 2018 · 0 comments
Labels
fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill

Comments

@hiroshige-g
Copy link

How about introducing a predefined layered API (say std:test) for testing Layered API infrastructure?

std:test does something (i.e. has a side effect when evaluated), such as incrementing a global variable.

This can be used for example:

  • When std:test|https://fallbackA.com/ and std:test|https://fallbackB.com/ are imported, then std:test should be evaluated only once. In other words, this is testing that std:x|y resolution happens before module map and the key in the module map is std:x, not std:x|y.

Also, this can be used to test that importing std:x actually works (i.e. evaluates std:x's script) in a simple fashion.

@domenic domenic added the fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill label May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill
Projects
None yet
Development

No branches or pull requests

2 participants