📝 Show child attributes diction

[JFWooten4]

Do you think it's intuitive to scroll through the specification to find a box you need to click to see the most basic information about a price_r object?

Given the amount of information concealed here is so minimal, I really think it should get displayed as a simple sub-list. 🖥️

stellar-docs/docs/data/horizon/api-reference/resources/offers/object.mdx

Lines 37 to 42 in 7b5567b

	- n
	- number
	- The numerator.
	- d
	- number
	- The denominator.

Moreover, the verbose Show child attributes phrase adds practically as much requite reading as the fundamentally-crucial numerator and denominator definitions themselves. 🧐

[Epic-SX]

Hello.
I am interested in issue.
I can complete this issue.
I would appreciate it if you give me opportunity to work with you.

[ElliotFriend]

Hey, there!! You do bring up a good point that the "hiddenness" of the child attributes in this instance doesn't really serve much purpose. I think it's more intuitive what it was meant for on pages like The Claimable Balance Object, where a couple layers of child attributes are nested together.

That said, this will probably be irrelevant in the not-too-distant-future. Soon, we'll be generating these pages out of the OpenAPI spec files, instead of hand-writing them. They'll be displayed similar to this example schema page, and it'll feel a lot like the existing OpenAPI parameter/response sections that are already displayed alongside each of the endpoint pages.

[JFWooten4]

@ElliotFriend which PR was it that ended up implementing the OpenAPI? This is the first time I've seen it used on an intimate level, and would love to explore the path-routing specs for #723.