Adding back reflection code for smoother end user experience

[xarpen]

Hi,

I'm using many different packages in my projects using OpenUPM.
It's rather inconvenient to have the installer in the project that you need to do some post importing manipulation (running Install package).

In the big team it's really quickly becomes a problem, and I would rather have some standard package that does not require any of it.
Now I understand the idea behind the bridge and that it makes the code better, however I wonder if the price to pay is too much for the regular user? I understand it's not a big deal to import it, but it might be show stopper for some people (especially if you need to manage big development cycle).

In my fork, I simply embedded the bridge to the package (I don't use DOTS), however I was thinking about reverting some of your reflection code back.
Do you think there would be any use of this in the main repo? Maybe some shielded #ifdef classes that can be drop-in replacement for the bridge, and if people want to use the bridge they can also? (ie default behaviour is to use reflection code)

Thanks,
xarpen.

[vanifatovvlad]

Starting from v1.12.0 Tri Inspector does not require any post importing manipulation