Heath C

@abemedia This PR has conflicts, is missing updates to the test snapshots and, I'm also interested in seeing a screenshot of the before and after

With the v5 beta, maybe this is fixed, otherwise I'm open to helping you write a fix

@AlimovSV FYI, the upcoming beta (landing in about a week) completely refactors all of this code in breaking ways. If you'd like to make the fix in a code base...

@jbcpollak Can you check to see whether this is still an issue in the v5 beta?

@dchenk Due to the upcoming v5 release, the `PrimeReact` PR will need some work due to all of the breaking changes. I am willing to work with you to get...

@dchenk I'm pretty busy just getting 5.0 ready. Once I have finished writing up the migration guide, you hopefully could make the necessary changes.

@dchenk Ok, v5 beta has landed. There are some new templates that will hopefully make things a little easier. See the [5.x migration guide](https://react-jsonschema-form.readthedocs.io/en/latest/5.x%20upgrade%20guide/) as well as the expanded [custom...

@luisrafaelmartins13 This is a good fix, unfortunately the v5 beta refactored the `utils.js` into its own `@rjsf/utils` package and thus these changes will need to be refactored there.

Closing as this was fixed in https://github.com/rjsf-team/react-jsonschema-form/blob/eb577da7da1fabaa43c8954256c6c51cea6eea69/packages/utils/src/findSchemaDefinition.ts#L52

@memalloc Given the changes in v5 beta, the code here needs refactoring. Is this something you are willing to do?