HttpRepl
HttpRepl copied to clipboard
[Feature Request] Support OData $metadata document for API discovery
Similar to Open API specification, OData endpoints provide the $metadata endpoint. When using HTTP REPL as a debug-helper tool to consume APIs from an OData endpoint (e.g. SharePoint Online), it would help if the tool could read the $metadata document and provide simplified navigation similar to what you get when you connect to a REST API with an Open API definition.
OData would not need to be queried by default, but I'd suggest adding a new connect-odata command which does the same thing as connect does, but tries to discover an OData $metadata specification instead.