Allows for a custom tagName to be used in place of "form"

[juliankigwana]

Reasons for making this change

Sometimes we need a way to nest the RJSF components so that we can utilise the rendering capabilities within our components. For example, when rendering a custom Array<Object> component, the child properties can be rendered in a child form. However doing this will produce invalid html, a nasty error in the console, and possibly cause unforeseen problems across browsers.

Checklist

• I'm updating documentation
  • I've checked the rendering of the Markdown text I've added
• I'm adding or updating code
  • I've added and/or updated tests
  • I've updated docs if needed
• I'm adding a new feature
  • I've updated the playground with an example use of the feature

[epicfaace]

Looks great, thanks! Can you add a test for it?

I'm also wondering if not having a form tag will break anything (such as event handlers) -- nothing comes to mind, but let me know if you think of something.

[juliankigwana]

I added a test. I cannot think of any obvious other than the default native browser behaviour might not work. But I would imagine that if you were manually changing the tagName, then you would be aware of this.

[epicfaace]

@juliankigwana that makes sense. Can you add that bit as a warning in the documentation? (that the native browser behavior might not work)

[epicfaace]

Additionally, the only allowed values for tagName will be valid JSX HTML tags, correct? Can you add a test in which one tries an invalid tagName?

[juliankigwana]

Additionally, the only allowed values for tagName will be valid JSX HTML tags, correct? Can you add a test in which one tries an invalid tagName?

I'm not sure we can test for it. Most browsers will render an unknown banana tag as a block element. It would be up to the developer to know what is valid HTML.

I shall update the documentation with the warning and something saying it expects a valid HTML tag.

[epicfaace]

Makes sense, thanks! Can you apply this suggestion -- and then we'll be good to merge this.

[juliankigwana]

Thanks @epicfaace. I did apply the suggestion, but it's still showing here as changes requested. Do I need to do anything else?

[epicfaace]

Nope, looks good -- thanks!