I just encountered this recently today and I still wonder if this is either a bug or a feature. I need some confirmation from the backend.
Pretty crucial for my off-Studio scripting session. I always read those wiki pages if I need something checked.
The Dev Hub was having issues recently. And the lack of inheritance being showed started to happen after they said they were resolving the issues.
I’ve noticed it as well, so I thought maybe they were still restoring pages on the Dev Hub since the entire API Reference was missing at one point. I do not think this is an intentional change.
Was going to make a thread about this until i found this one. It is very frustrating and annoying. And what if a new developer wants to find something out about an instance? it’ll be very confusing for someone who’s new to the wiki.
I’ve been using the way back machine and simply cross my fingers and hope there’s some data.
As a developer, I use the Developer Hub API Reference pages as a handy reference to find members of classes or refresh my memory. Now that the API reference no longer shows inherited properties/methods/events, its utility is severely decreased!
In the page for Part alone, one will not know about these members that are very important:
Although there is an object hierarchy in the sidebar, it does not center on the current class and is not easy to navigate due to its small size. These factors together make the API reference very inconvenient.
Wiki now shows no API whatsoever.
It has been 2 weeks without a fix to this, or even a staff member acknowledging this thread. It’s honestly hindering productivity.
3 weeks since the creation of this thread, and yet no fix or acknowledgement of the problem. What is Roblox doing?
I think this is mostly the wiki staff’s responsibility. Let’s wait a little more and see if any response pops up.
It seems that the devhub is no longer taking into account inherited members. The Part reference has nothing but the “Shape” property.
Thanks, this is a known bug that will be fixed very shortly!
It has been a month since a fix was promised, is it still going to take place? If so, when?
As a developer I use the developer hub almost exclusively for its API documentation. It is not currently useful for that purpose in any way shape or form. I am no longer able to look up basic information on objects I use on a daily basis. Many objects have next to no information available due to inherited API members not being displayed on their pages.
Here are a few of the pages that are barren and no longer offer any value. You’ll find text on some of these pages referencing API members not listed or accessible on the page. On most pages you will not find a single link to the class these objects inherit from to find the missing API members, and if one does exist it’s not placed in any obvious spot.
https://developer.roblox.com/en-us/api-reference/class/Part
https://developer.roblox.com/en-us/api-reference/class/Weld
https://developer.roblox.com/en-us/api-reference/class/ImageButton
https://developer.roblox.com/en-us/api-reference/class/ScreenGui
https://developer.roblox.com/en-us/api-reference/class/Accessory
https://developer.roblox.com/en-us/api-reference/class/AlignOrientation
https://developer.roblox.com/en-us/api-reference/class/SpecialMesh
https://developer.roblox.com/en-us/api-reference/class/Texture
https://developer.roblox.com/en-us/api-reference/class/LocalScript
https://developer.roblox.com/en-us/api-reference/class/Tween
These are all basic core objects people of all skill levels use on a day to day basis. Broken API pages for these objects (and many more not listed) severely inhibit and in some cases cripple a developers productivity and ability to create.
The following are extremely unfortunate situations that can occur from the absence of these inherited members. These are situations that everyone from beginners to experts will encounter when trying to use the dev hub as an API reference in its current state.
“I’m trying to fix a physics bug in my game, I was told to try the :SetNetworkOwner() function on Parts but the devhub doesn’t have information on it on the Part page.”
“I’m trying to make my shop button gui work, but I don’t know how to tell if it’s been clicked. There are no events (at all) about clicking listed on the dev hub.”
“I’m trying to play a sound when my tween finishes playing but the devhub page says there are no events for when that happens.”
If this problem is fixed myself and many others would be able to once again take proper advantage of the amazing resource that is the devhub. As of this post it will have been near 60 days since the issue was brought up, it’ll have been nearly that long since any update on the problem, and it will be moving towards 3 months that it’s been a problem in the first place.
My trick for it is clicking class tree on the left, then using CTRL + F to search for the class name, then going steps up the class ancestry. Of course, it’s impractical, but it’s better than nothing.
The site feels almost unusable without these tbh, I’ve been looking at alternatives the past few weeks instead.
This is very important to me and I hope it gets resolved soon. In the past, my immediate thought when I needed to find something relating to the Roblox API was to check the wiki, now with the developer hub I have to think twice about whether I should use that, the object browser, or another user’s third party documentation, to find what I need to do my job.
It’s very frustrating to encounter this on a regular basis. We’re in desperate need of resources allocated internally to make documentation usable again.
Had to spend a while figuring out Tween APIs and was very confused (see here). This should be high-priority on the fix list.
As a developer I want the developer hub to provide me with useful information about the features and objects I am looking up, but in its current state the hub does not fulfill that purpose at all. Here is another example of a page that is essentially ‘empty’.
https://developer.roblox.com/en-us/api-reference/class/UnionOperation
We should not have to deal with these kind of nuisances, especially given that the developer hub is essentially the only place for the majority of developers where they can find documentation about most features. An API or feature is pretty much useless if the developer hub is not even trying to tell us it exists.
For anyone wondering, the issue has been fixed.
Sorry for the long turn around time for this. We had the fix out much sooner but we had to roll it back due to factors unrelated from the patch itself, so the release got deferred while we fixed that problem. In the future big problems like this shouldn’t take so long to get fixed, this was just a bit of a special case.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
