Request: Please expose PropertyInspector

[left osprey]

I consider being able to write custom tooling very important for smooth development but it's completely locked down in entities as PropertyInspector is marked Internal and I don't think we should have to do something unsupported to write custom inspectors.

Unless there are plans to replace this with something else I don't really understand why it's not public. The workflow around this effectively hasn't changed in years, and in fact the previous version of this was even public in 0.17 however was changed for some reason to internal in 0.51.

[CreateProperty] etc is only good for basic cases, if you want to write interesting tooling you need actual element access.

A simple example of where PropertyInspector was very useful is what let me create an inspector for physics colliders which was recently replicated in the official physics package (they weren't even aware they could use this until it was pointed out #1143902923361882134 message ) but there are a magnitude of other use cases

A second bit more of a stretch request is to allow PropertyInspector (or provide an alternative) to work on DynamicBuffer<T> as a whole instead of per element. I've had to fork the entities package and make a small change to allow this to work (it's far from an ideal implementation as it re-uses the component variation)
https://github.com/tertle/com.unity.entities/commit/66fce05c3d8aa2d617b6883562a8bde7894337a9

This request is actually a lot more useful to me as it's where a lot of my recent custom editors comes from. For example, I really want to be able to add a search field to certain buffers because if have 200 elements in a buffer, it takes a long time to look through one at a time...

But also it let us to do really cool things like for example, I can now write a custom inspector for my DynamicHashMap (excuse the poor recording)

[left osprey]

Request: Please expose PropertyInspector

[left osprey]

example of what i mean by adding search etc, super useful