Heath C

@MarekBodingerBA Yes, or that.

@selfesteemteam If you call `getDefaultRegistry()` you should be able to pull out the `ArrayField` implementation and then wrap it with your own `CustomArrayField` by calling it. ``` import { FieldProps...

Rather than trying to import it from `core` you can obtain it from the `registry` using the following code: ``` import { getDefaultRegistry } from `@rjsf/core` const { fields: {...

@hannatorj Awesome, I will close this issue then

@shvekyha I see your PR in your fork... are you willing to create a PR against the RJSF main branch instead?

> i would like to work on this issue as my first contri @Soudarjya I'm looking forward to seeing your PR. Let me know if you have any questions

The widget has access to the `formData` at its current level (in your example the widget will get the value for `name`) via the `value` prop. Is there a reason...

@zzph I'm wondering if the "freezing" of the form you are seeing is a situation where your the state change causes a rerender infinite loop. Theoretically, you should be able...

Maybe you can process the formData on change in a way that you transform what you put into the formContext is only what you need to provide the `auto-suggest`? Meaning...

What if you use a React context to store the form data rather than `formContext` and access it specifically from your widget, via the `useContext()` hook?