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

Test abstraction references #389

Open
leobalter opened this issue Nov 20, 2019 · 2 comments
Open

Test abstraction references #389

leobalter opened this issue Nov 20, 2019 · 2 comments
Labels
c: meta Component: intl-wide issues s: help wanted Status: help wanted; needs proposal champion

Comments

@leobalter
Copy link
Member

Raw idea:

  • ECMA-402: Every build will check references in the glossary, failing if not found in ECMA-262.
  • ECMA-262: Every build will import the references from glossary files we mark (checkout repo's default branch and lookup). Instead of a failure, warn if new changes affect references.

This avoids a vicious cycle if we actually need to change abstraction names.

Originally posted by @leobalter in #387 (comment)

@sffc
Copy link
Contributor

sffc commented Mar 20, 2020

To be clear, this bug is suggesting that we add/improve continuous integration testing on the repo?

@sffc sffc added c: spec Component: spec editorial issues s: help wanted Status: help wanted; needs proposal champion labels Mar 20, 2020
@sffc
Copy link
Contributor

sffc commented Jun 5, 2020

CC @ljharb @gibson042

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: meta Component: intl-wide issues s: help wanted Status: help wanted; needs proposal champion
Projects
None yet
Development

No branches or pull requests

2 participants