Grigas

> I plan to use the Symbol approach unless somebody sees some fatal problem with it. Not sure if this is a problem in `itwinjs-core`, where all packages are tightly...

> As stated above, one of the main concerns with moving forward w/ these changes is the docs site. I would say that not having those props and return types...

> @grigasp I'm not sure I agree on the removal of the return interface structures that are output from the API. This would lead people to not know what it...

Not an issue to packages in `itwinjs-core`, but turns out symbols can't be used in React props interfaces. So for react packages this approach doesn't work.

Sentry is still reporting crashes, reopened the issue.

Call stack in [this crash event](https://bentley-systems-inc.sentry.io/issues/5315708082/events/472b73ca92364a2db385834f67d354a5/?project=1520306) shows that `NativeECPresentationManager` destructor is being called without first calling the `Terminate` method. In addition, based on what happens further, it seems there are...

> Need ECPresentation performance testing as prerequisite to merge. I'll try to find some time for this ASAP, but that'll probably only happen next week.

Not good... Here're the results: | Test case | 4.11 | 5.0-dev.115 | 5.0-affan | 5.0-affan-analyzed | | ----------- | ------ | ----------- | --------- | --- | | L...

@khanaffan, based on our internal discussion, I re-ran the test on the test iModels after running `ANALYZE` on them, using the addon built from this branch. The results are better...

> Well, it just means that application will be even more hesitant to consume packages, because they will always see major version bumps. But, yeah, in some sense, it also...