-
Notifications
You must be signed in to change notification settings - Fork 27
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
Consider more name change fallout from 'if' --> 'assert' rename #87
Comments
We might want to update Mozilla's position |
Other parts of spec text also reference "conditions" ( |
I landed #88 and posted an update to mozilla/standards-positions#373 (if they want to change it I'll offer to submit a PR; I'm not sure if creating a PR against mozilla/standards-position as a non-Mozilla employee presumes too much 😄). So, closing this. |
@dandclark I think it's ok to do it, like I did mozilla/standards-positions#392. I'm happy to send a PR |
@xtuc Oh, I didn't notice it was done that way last time. Looks like dbaron beat us to it though: mozilla/standards-positions@da63152 |
#80 changed the keyword from
if
toassert
. There are two other name changes to consider as follow-ups:[[Conditions]]
fields to[[Assertions]]
Thoughts/objections/any other changes we're missing?
The text was updated successfully, but these errors were encountered: