ReflectionService:GetPropertiesOfClass() lacks information about whether a property is hidden or not

[LuauWebService (MainIsBannedInForum)]

There is currently no information that ReflectionService:GetPropertiesOfClass() returns about if a property is a hidden property or not, and there are no other ways for developers to filter out hidden properties other than manually creating a list of hidden properties to exclude.

For example, the Velocity property of a part is a hidden property, as shown below:

However, the GetPropertiesOfClass function lacks information about if the property is hidden or not:

                    [81] =  ▼  {
                       ["Display"] =  ▼  {
                          ["Category"] = "Data",
                          ["DeprecationMessage"] = "Use `AssemblyLinearVelocity` instead."
                       },
                       ["Name"] = "Velocity",
                       ["Permits"] =  ▼  {
                          ["Read"] = 0,
                          ["Write"] = 0
                       },
                       ["Serialized"] = true,
                       ["Type"] =  ▼  {
                          ["EngineType"] = "Vector3",
                          ["ScriptType"] = "Vector3"
                       }
                    }

Expected behavior

ReflectionService:GetPropertiesOfClass() should return information if a property is hidden or not.

[MightyDantheman (Fate)]

Introducing ReflectionService: Programmatic Access to Engine API Information

@ExtraBreakfast @tnavarts Will we get more information regarding tags? How do I filter out properties that would normally be hidden (and have the Hidden tag)? Could we get Property.Tags like we would with an API dump? Also, what about predefined SecurityCapabilities? Instead of just .new() and .fromCurrent(), why not also have some common ones like .fromClient() (could also be called .fromLocal()), .fromServer(), and .fromPlugin()?

I feel like there should be a section just for tags. Deprecated properties should also be a tag for consistency, though at least DeprecationMessage is usable for that. But there are properties like ReceiveAge that don’t have any sign of being hidden, or otherwise different than any other normal property. There’s other missing tags, too, such as read/write safe for parallel.

[GroupyClumpy]

Very sorry for the late reply, but this is not a bug. Please file a feature request for this additional information to be included in the output of the API. Thank you!