Customizations allow you to use custom logic for leaves of your view/form generation. When a tagged sexp_grammar is encountered, apply_to_tag will be invoked on the tag's key and value. If apply_to_tag returns true, then the custom logic will be used in place of the default auto-generated logic.

form takes a type 'a and its sexp grammar and produces a 'a Form.t.

on_set_error defaults to Effect.print_s and allows customization of what happens if Form.set produces an error while operating on the sexp representation of the type. For types which derive sexp and sexp_grammar, on_set_error should not be called, but it may for types with hand-rolled grammars or sexp functions.

customizations is a list of customizations to use while generating the form (see above). Customizations are tried in the provided order, using the result of the first matching customization.

Grammar fields tagged with key Ppx_sexp_conv_lib.Sexp_grammar.doc_comment_tag will be converted into tooltips. This tag is added automatically to doc comments on types which derive sexp_grammar with the ~tags_of_doc_comments option.

If textbox_for_string is supplied, string inputs will be textboxes rather than textareas (meaning the form can be submitted with Enter when those fields are active, but users will not be able to input multiline strings).

allow_duplication_of_list_items defaults to true and controls whether a "duplicate" button is shown next to all list as a shortcut to duplicate that item in the list.

form' is similar to form, but takes an untyped sexp grammar as a value, and produces a Sexp.t Form.t. This allows you to create a form that depends on a dynamic sexp grammar.

view_as_vdom provides a custom rendering function for the form generated by form, which is optimized to look good, even with many levels of nesting.