8000 Specify validation for new features · Issue #93 · tc39/ecma426 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Specify validation for new features #93

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.

Sign up for GitHub

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

Jump to bottom
Open
jkup opened this issue Jun 13, 2024 · 0 comments
7CFE
Open

Specify validation for new features #93

jkup opened this issue Jun 13, 2024 · 0 comments
Labels
discussion

Comments

@jkup
Copy link
Collaborator
jkup commented Jun 13, 2024

We don't want to break backwards compatibility, so we have agree to never do things like codify into the spec that version has to be the integer 3. I think we all agree on that?

We should discuss if we want to begin introducing "validation" text to the specification for new features. For example, with Scopes, should the specification text say that GeneratedPosition must only contain a line and column and they both must be numbers?

I just want to kick of a discussion about how much we add "validation" language to the specification for new features.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jkup
0