You’re right - moving to a new API docs system with less information definitely does not make sense. That’s why we have tools to measure how good things are*, and over time we’ve made demonstrable leaps and bounds with regards to existing documentation. It is holistically untrue to call the devhub a net downgrade in comparison to the wiki.
That said, you’re correct - this is one “con” that we also agree needs to be fixed. Clearly, the discussions have been made regarding this one feature and it’s been prioritized accordingly.
Part of what makes good documentations is the inclusion of more than just names and types; good docs also include good descriptions as well. In the meantime, we’ve made sure that many (many many many) descriptions have been updated; so in cases like these where ClassNames of Instances are missing, there’s (almost) always more information in a paragraph description. Until a complete solution is found re: the API dump, we still have the power of writing a good text description.
Also @YellowoTide regarding PathFindingService - this API is going to get some love taps in the very near future. Holding off on updating those pages until those changes are ready.
P.S. I hope everyone stops calling the new devhub “the wiki” sometime soon…since It’s not a wiki. It’s not even close to a wiki - It just fills the same need as the wiki did.
* edit: quick addendum - such tools cannot tell (without an upgraded API dump) whether the problem described in the OP is happening. So, as far as I know, we don’t have a number for how many methods this affects.