Not a great idea IMO, since that'd make it much harder if we ever wanted to use a signal to return the field types (like we do in surveys, contrib fields, etc) instead of supporting only a hardcoded list.
can we avoid replicating all the config forms here and just use the ones of the base fields? i think you are only replicating them to get rid of description but keeping a description wouldn't be so bad IMO! (on the review page we could show it as an info tooltip for example)
This title = StringField(_('Title'), [DataRequired()], description=_("The title of the field")) from FieldConfigForm makes a little bit of a problem. Since in the context of reviewing fields Title for the field label is wrong.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.