Problem. With @netscript/fresh/form, the managed <Form>'s FormElementProps doesn't accept class/arbitrary attributes on formProps — you must pass class as a top-level <Form> prop, which is surprising and cost debugging time in VS3's create-session form.
Proposal. Widen FormElementProps to accept class + standard <form> attributes (or, minimally, document the top-level-prop contract).
Surfaced during the eis-chat v2 refactor (netscript alpha.18). Promotion candidate → @netscript/fresh-ui / web-layer.
Problem. With
@netscript/fresh/form, the managed<Form>'sFormElementPropsdoesn't acceptclass/arbitrary attributes onformProps— you must passclassas a top-level<Form>prop, which is surprising and cost debugging time in VS3's create-session form.Proposal. Widen
FormElementPropsto acceptclass+ standard<form>attributes (or, minimally, document the top-level-prop contract).Surfaced during the eis-chat v2 refactor (netscript alpha.18). Promotion candidate →
@netscript/fresh-ui/ web-layer.