You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by kentbulza January 28, 2024
This seems like an obvious gap to me, but I want to see what were the philosophical reasons for it. Perhaps because the webhooks object is newer, it just wasn't as obvious at first that the info object can be awkward? The issue is there may be very different global(esque) descriptive text for all the paths vs. all the webhooks.
The concern here is about describing Paths and Webhooks separately. It's possible to put each in separate documents with separate Info Objects, but it is not possible to reference an entire Paths Object (or the entire contents of the webhooks field, which isn't a named Object in 3.1). I could see solving this by either adding these fields (they cannot be confused with path templates, although that doesn't help with the object under webhooks) or the much larger change of allowing referencing groups of Paths (which might be deemed too big to do prior to Moonwalk
The text was updated successfully, but these errors were encountered:
Discussed in #3532
Originally posted by kentbulza January 28, 2024
This seems like an obvious gap to me, but I want to see what were the philosophical reasons for it. Perhaps because the webhooks object is newer, it just wasn't as obvious at first that the info object can be awkward? The issue is there may be very different global(esque) descriptive text for all the paths vs. all the webhooks.
The concern here is about describing Paths and Webhooks separately. It's possible to put each in separate documents with separate Info Objects, but it is not possible to reference an entire Paths Object (or the entire contents of the
webhooks
field, which isn't a named Object in 3.1). I could see solving this by either adding these fields (they cannot be confused with path templates, although that doesn't help with the object underwebhooks
) or the much larger change of allowing referencing groups of Paths (which might be deemed too big to do prior to MoonwalkThe text was updated successfully, but these errors were encountered: