[dannote]

Found through PhoenixVapor, comparing its server render with Vue's own server renderer (@vue/server-renderer) on the same templates.

Reserved attributes

split_template/2 printed a static ref or key as an attribute (<input ref="search">), and passed ref and key to components and root attributes as props. Vue reserves both and never renders them. A bound :key was already left out; now ref and key are, static or bound, in attributes/4 and props/3.

<select v-model>

A select's v-model produced a warning and no slot, so a renderer couldn't mark the selected option. Vue's server renderer outputs <option value="b" selected>. Now each <option> inside a <select v-model>, in an <optgroup> or a v-for too, has a :model slot in its start tag, tag: "option", carrying:

• the select's model expression as :value;
• the option's own value, in this order:
  • its bound :value, as the slot's new :option_value field (an addition to encoded_model_slot, regenerated with RustQ);
  • its value attribute;
  • its text, as Vue values an option without one.

An option outside a <select v-model> has no slot.

PhoenixVapor's side renders selected on a match (Vue's looseEqual, membership for multiple), checked against this branch: the output now matches Vue's for ref, ref_for, ref_key, key and the select.

Checks

mix lint (rustq.gen --check, format, credo, ex_dna, reach, dialyzer, cargo fmt, clippy -D warnings) clean; mix test: 137 passed (11 doctests), with new tests for both. PhoenixVapor's suite on this branch: 381 passed.