@knolleary I saw in another thread you said you'd updated the docs and wanted some feedback.
I'm also not clear in the first clip above if $(.input). would ever be used as I understood it would always be of the form #node-input-.
If there is to be only one type, does the types array need to be defined (Clip 2 above).
My other thought is that I still do not understand why I would use the typeField. I have experimented but cannot see what impact it has. Some additional explanation and perhaps an example would be useful.
Just the view from coming to this for the first time - I understand how hard documentation is :).
Im sure you read the explanation in the docs but just in case...
In some circumstances it is desirable to already have an <input> element to store the type value of the typedInput. This option allows such an existing element to be provided. As the type of the typedInput is changed, the value of the provided input will also change.
To paraphrase - if you add a hidden input element & provide it's selector to the typeField property, the typedInput will store your selection for you, meaning (for example) you don't need to save it's value manually in oneditsave