replace keyword from with to if

[xtuc]

Refs #3

[xtuc]

I will also update the syntax section of the README with an explanation before we merge this.

[ljharb]

not that it's really up to this proposal, but withtype/iftype seem weird to me; i'd expect if-type or if:type or something else that indicated a hierarchy.

[littledan]

The name here is intended to match HTML attribute naming conventions. See https://w3ctag.github.io/design-principles/#casing-rules

[ljharb]

that talks about concatenating multi-word things, like "max length" - "if type" isn't a single word, it's a hierarchy, and it is very not clear to me that "iftype" is the thing these principles dictate. it seems more like this is a case those principles simply haven't considered.

certainly this PR/repo isn't the place to discuss it tho :-) i'd appreciate a link, if you have one and when the time is relevant, to the appropriate place

[littledan]

Would it be OK if the MVP web integration did not include specifying import attributes on the script tag? I think this can be delayed until we have a type on the web that motivates the use case.

[xtuc]

I think showing the HTML example illustrate possible uses cases, but maybe we should make it clear that it's not meant for TC39?

[ljharb]

Isn’t JSON the web type motivating the entire proposal?

[littledan]

Yes, initially (though other module types are also considered part of the motivation), and it does not make sense to have a script tag with a JSON module--it would not do anything, since there's no way to get the exports out of a module in a script tag.

[xtuc]

I added a sentence to make it clear that it's outside of TC39

[littledan]

LGTM, but please write in the explainer that the if name is designed to explain/evoke the "check" semantics, and that one could imagine a separate with section as a follow-on proposal for "evaluator" attributes.